'file' gives me exactly that output indeed. Pd says nothing more than:
C:/Program Files (x86)/pd/startup/gvf: can't load startup library'!
So that's pretty useless.
2013/11/6 IOhannes m zmoelnig zmoelnig@iem.at
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-11-06 15:52, Bas Kooiker wrote:
Oh yeah, I forgot about that. Will do next time!
Getting cygwin 32 worked! I succefully built the dll. But now the library can't be loaded in Pd. The dll is created in the folder Build/CYGWIN_NT-6.1-WOW64/. Does the WOW64 mean it is still a 32 vs 64 bit problem?
hard to tell. WOW64 is actually the wrapper for running 32bit applications on 64bit windos, so it should be corrct.
un unix there is a utility called "file", which should tell you what the file is. if "file" exists for cygwin, you *should* get something like this: $ file Build/CYGWIN_NT-6.1-WOW64/gvf.dll Build/CYGWIN_NT-6.1-WOW64/gvf.dll PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
but ther ecan be numerous reasons why the loading fails. do you get any specific errors?
fgmasr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJSembDAAoJELZQGcR/ejb43iQQAIGfAOyV6A0EW1T8WNvpXUoE 9TEMCTTn/o7PSTP5b56uG59rdgoSI2CwkvIRj4eWiL0B8eiaZqO1yXl0YcPuuJCW xcBMUDclSUKUrCQ5mQGusQILAXIDIX8P6PR2/dv3mhuG5eScKt3dAFaHa9BO33Sv UtumZ5BUpEOCKrJ1Ux00+em4WUsfxiSw2L6KfK5iFVIw7RAxNCtP+4MzCs9INvT5 roQmnSs4XFuQ+0ZKhixlLQvgPDVIeug6/HE4FkJBenYC0NyEf+gtXgSniVwsiJ55 OzhgtJsrZGg1L0fH+hqD9Z/ugUKdyPvM34LC3qL6zDBStK6MPjhWCTaK2gj4gB9H v2CrJnkfK/XmU/FeZeZlsXFjIPfnMEDj4ns/XKO4QSWQXhOBN6NV8osD5i97Dsk3 jW9vRZzv8PsMmuciL4jXP4hp3KdBNisZykbO4XAot1yV8hfplI3gosNSnJlL3J8J ObpE5UKXtOhXoovYc92aPy4bZWSH1uIjrrDkjMvCUJ4gMnsx2XVd9r6JPjWjW7mJ rWsn/uhUASvPF9j7QNgmbNQhx9ttVpG8VgnJGx/S98tRh3fDX4i9Oj+ni01DrcaD +Mcs/WDvUJ+dPnRCiB+ug0rqrV12QFWh3FvyIN75R81U21n6/fWnlK6fkSwW83jW sxxcEryGJs4CDAKl3RKe =dzgE -----END PGP SIGNATURE-----
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev