Re: [ft] Compiling freetype 2.3.9 with bcc fails

Hi, Compiling test.c fails: bcc32 -ohello.exe hello.c CodeGear C++ 5.93 for Win32 Copyright (c) 1993, 2007 CodeGear hello.c: Turbo Incremental Link 5.81 Copyright (c) 1997-2008 CodeGear Fatal: Unable to open file 'HELLO.OBJ' This works: bcc32 hello.c CodeGear C++ 5.93 for Win32 Copyright (c)

Re: [ft] Compiling freetype 2.3.9 with bcc fails

generates a.out from hello.c, but bcc32 generates hello.exe from hello.c by default. So if I use -n and leave the output filename for compilers' default, we don't know the output filename. Regards, mpsuzuki On Tue, 14 Jul 2009 08:40:54 +0200 Mirco Babin mirco.ba...@gmail.com wrote: Hi

Re: [ft] Compiling freetype 2.3.9 with bcc fails

use /P with the next available higher page size. Regards, Mirco 2009/7/14 Mirco Babin mirco.ba...@gmail.com Hello mpsuzuki, I started from scratch, unzipping freetype-2.3.9.tar.gz. I applied your patches to bcc.mk, bcc-dev.mk, win32-def.mk and exports.mk Then I ran mingw32-make

Re: [ft] Compiling freetype 2.3.9 with bcc fails

),$(PROJECT_LIBRARY)) -LINK_LIBRARY = tlib /u $(subst /,$(COMPILER_SEP),$@ $(OBJECTS_LIST:%=+%)) +LINK_LIBRARY = tlib /u /P128 $(subst /,$(COMPILER_SEP),$@ $(OBJECTS_LIST:%=+%)) # EOF On Tue, 14 Jul 2009 13:21:53 +0200 Mirco Babin mirco.ba...@gmail.com wrote: I tried the TLIB /u

Re: [ft] Compiling freetype 2.3.9 with bcc fails

compilers generates a.out from hello.c, but bcc32 generates hello.exe from hello.c by default. So if I use -n and leave the output filename for compilers' default, we don't know the output filename. Regards, mpsuzuki On Tue, 14 Jul 2009 08:40:54 +0200 Mirco Babin mirco.ba...@gmail.com

Re: [ft] Compiling freetype 2.3.9 with bcc fails

) 1997-2008 CodeGear Fatal: Unable to open file 'APINAMES.OBJ' mingw32-make: *** [objs/apinames.exe] Error 1 Regards, Mirco 2009/7/13 Mirco Babin mirco.ba...@gmail.com Hi, I applied your patch and compiled. I see the -L now, but it still results in an error. I believe the -L./objs should

Re: [ft] Compiling freetype 2.3.9 with bcc fails

bcc32 -Lobjs -oobjs/apinames.exe src/tools/apinames.c and it successfully finihsed - the pathname separator in your experiment was really /, not \? Regards, mpsuzuki On Mon, 13 Jul 2009 08:50:59 +0200 Mirco Babin mirco.ba...@gmail.com wrote: Hi, Update, I manually changed

Re: [ft] Compiling freetype 2.3.9 with bcc fails

Hi, I don't know the makefile syntax. I just find it much too complex. You seem to understand this rather obfuscated language, so I believe you when you say that I may not remove the apinames.exe. If you can give me an adjustment for the apinames.exe, so it's a 2-phase step, first compile,

[ft] Compiling freetype 2.3.9 with bcc fails

Hello, I'm having troubles compiling freetype 2.3.9 with Codegear Rad Studio 2007 (bcc32). I followed the next steps: mingw32-make.exe setup bcc32 mingw32-make.exe The second step fails upon linking APPNAMES. The output I get is: Kan c:\a\open\PoDoFo\freetype\objs\ftmodule.h niet

Re: [ft] Compiling freetype 2.3.9 with bcc fails

, Mirco 2009/7/10 suzuki toshiya mpsuz...@hiroshima-u.ac.jp Hi, Mirco Babin wrote (2009/07/10 20:24): bcc32 -oobjs/apinames src/tools/apinames.c CodeGear C++ 5.93 for Win32 Copyright (c) 1993, 2007 CodeGear src/tools/apinames.c: Turbo Incremental Link 5.81 Copyright (c) 1997-2008 CodeGear