I believe the reason ftexport.sym is ignored is pretty much the same … check this out:
alex@ALEXANDERAG6A39 ~/freetype-2.6 $ ./objs/apinames.exe -o/home/alex/freetype-2.6/obj/ftexport.sym /home/alex/freetype-2.6/include/freetype/ttnameid.h /home/alex/freetype-2.6/include/freetype/freetype.h could not open '/home/alex/freetype-2.6/include/freetype/ttnameid.h' for writing and no ftexport.sym is created. At the same time: alex@ALEXANDERAG6A39 ~/freetype-2.6 $ ./objs/apinames.exe -o ./objs/ftexport.sym /home/alex/freetype-2.6/include/freetype/ttnameid.h /home/alex/freetype-2.6/include/freetype/freetype.h unable to open '/home/alex/freetype-2.6/include/freetype/ttnameid.h' unable to open '/home/alex/freetype-2.6/include/freetype/freetype.h' PANIC: could not find exported functions !! And both of the following seem to work: alex@ALEXANDERAG6A39 ~/freetype-2.6 $ ./objs/apinames.exe -o ./objs/ftexport.sym ./include/freetype/ttnameid.h ./include/freetype/freetype.h alex@ALEXANDERAG6A39 ~/freetype-2.6 $ ./objs/apinames.exe -o `cygpath -w /home/alex/freetype-2.6/objs/ftexport.sym` `cygpath -w /home/alex/freetype-2.6/include/freetype/ttnameid.h` `cygpath -w /home/alex/freetype-2.6/include/freetype/freetype.h ` Not to change the topic, but I’ve tried some alternative methods of building. Under the same environment as above (cygwin with mingw toolchain), cmake seems to go further, but doesn’t seem to offer disabling zlib. Switching to msys2 shell with mingw toolchain, the build is finishing, but the binary ends up requiring libgcc_s_dw2-1.dll — passing —static-libgcc in LDFLAGS doesn’t seem to have any effect. On November 27, 2015 at 12:24:42 PM, Werner LEMBERG ([email protected]) wrote: > Running into some problem building freetype for Windows under > cygwin, using mingw compiler. The problem seems to be with build > process launching an Win32 executable, and passing Cygwin paths to > it, resulting in: > > > /home/alex/freetype-2.6/objs/apinames.exe \ > -o/home/alex/freetype-2.6/objs/ftexport.sym \ > /home/alex/freetype-2.6/include/freetype/ttnameid.h \ > [...] > > could not open '/home/alex/freetype-2.6/include/freetype/ttnameid.h' > for writing This is *very* strange! Why does the `ftexport.sym' argument gets ignored, making apinames try to write to `ttnameid.h'? On my GNU/Linux box, this works just fine, and we've never got a error report, and the corresponding source and Makefile code is essentially unchanged since years... Please try to manually call /home/alex/freetype-2.6/objs/apinames.exe \ -o/home/alex/freetype-2.6/objs/ftexport.sym \ /home/alex/freetype-2.6/include/freetype/ttnameid.h \ /home/alex/freetype-2.6/include/freetype/freetype.h and check whether `ftexport.sym' contains identifiers. Werner
_______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
