Package Details: mingw-w64-glew 2.0.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-glew.git (read-only)
Package Base: mingw-w64-glew
Description: GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
Upstream URL: http://glew.sourceforge.net/
Licenses: Modified BSD/MIT/GPL
Submitter: None
Maintainer: xantares
Last Packager: xantares
Votes: 8
Popularity: 0.000145
First Submitted: 2011-09-06 14:33
Last Updated: 2016-07-26 06:57

Latest Comments

xantares commented on 2015-02-04 18:46

hello,
-the provedes line is useless:
provides=('mingw-w64-glew-lib32' 'mingw-w64-glew-pure64')
- please strip libraries
xan.

netz commented on 2014-09-12 03:45

Yeah, out of date and the current PKGBUILD leaves references to ${pkgdir}; I've updated a bit and cleaned out those issues:
https://gist.github.com/ntzrmtthihu777/fa7a26e4e79172f14a2c

laftur commented on 2014-01-03 09:52

@naelstrof: Sorry, I meant to ask why this package doesn't build the mx libs. GLEW MX features thread-safe support for multiple rendering contexts. Is there a reason why libGLEWmx is provided by the x86_64 glew package in the official repo, but not by the multilib package, or this package for mingw-w64?

laftur commented on 2014-01-03 09:50

@naelstrof: Sorry, GLEW MX features thread-safe support for multiple rendering contexts. Is there a reason why libGLEWmx is provided by the x86_64 glew package in the official repo, but not by the multilib package, or this package for mingw-w64?

laftur commented on 2014-01-03 09:48

Sorry, GLEW MX features thread-safe support for multiple rendering contexts. Is there a reason why libGLEWmx is provided by the x86_64 glew package in the official repo, but not by the multilib package, or this package for mingw?

laftur commented on 2014-01-03 09:40

@naelstrof: Sorry, maybe I misunderstand something. Is there a reason why libGLEWmx is provided by the x86_64 glew package in the official repo, but not by the multilib package, or this package for mingw?

naelstrof commented on 2013-11-25 02:59

Added staticlibs. @laftur: What do you mean by include? And what are the mx libs?

laftur commented on 2013-11-22 06:50

Would you be so kind as to
also include the mx libs? :)

xantares commented on 2013-10-31 07:49

Hi,
Care to add staticlibs in the options array ?
xan.

Anonymous comment on 2011-12-22 20:27

I thought that it would make more sense to split them like the regular libraries (with lib32, etc.) while the compiler is still multilib and one package. I will, however, try and make a combined package instead.

rubenvb commented on 2011-12-22 17:53

Would it bee possible to build one package for both x86_64 and i686? I didn't split the cross-compiler because I believe it'll cause confusion. Please don't split your packages. Two simple loops over the target triplets (like in all of thee cross-compiler packages) should do fine.

Thanks!