hi, I found a workaround by putting the allocation in a #ifndef _WIN32 statement pthread_t is a structure under windows and not only a 64bit int.
with pd-vanilla I got : "C:\\MinGW\\msys\\1.0\\home\\antoine\\pd\\pd-vanilla\\extra\\Gem\\Gem.dll: couldn't load Gem: can't load library" on startup... maybe because pd was build using microsoft compiler and Gem with MinGW I also managed to produce a Gem.dll form Microsoft Visual C++ 2010 Express and this time Gem loads in pd-vanilla 0.45.2 and it seems to work ! but i am wondering if i am doing right : Gem claims that some dll are missing and I added them directly to the Windows\System32 folder should I include them in the Visual Project instead ? + a -- do it yourself http://antoine.villeret.free.fr 2013/9/12 IOhannes m zmoelnig <zmoel...@iem.at> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2013-09-12 09:05, Antoine Villeret wrote: > > hi, > > > > I tried to build Gem under Windows 7 with MinGW. > > cool. > last time i tried, i *could* successfully compile Gem on w7/mingw. > i'll have a look into your problem asap. > > in any case, there is a substential problem with the MinGW build, and > that is that all the Direct* plugins will *not* work. > that is: no DirectShow video and movie sources. > the rest *should* work just fine. > > fgmasdr > IOhannes > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.14 (GNU/Linux) > Comment: Using GnuPG with Icedove - http://www.enigmail.net/ > > iEYEARECAAYFAlIxbNQACgkQkX2Xpv6ydvRlfACg7fbMx3YiUAK6Cv76iYjJZ1Xw > RrEAn2DzcM0zBolscgpaMv4/Bv2l3oL3 > =fvN1 > -----END PGP SIGNATURE----- > > _______________________________________________ > GEM-dev mailing list > GEM-dev@iem.at > http://lists.puredata.info/listinfo/gem-dev >
_______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev