Re: [ft] Compiling freetype 2.3.9 with bcc fails

[mpsuzuki]

Hi,

Considering the fact that "-L./objs" does not work,
I guess bcc32 cannot recognize "/" as valid pathname
separator. If my guessing is right, the expected
might be:

        bcc32 -Lobjs -oobjs\apinames.exe src\tools\apinames.c

You've ever written that you tried

        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 <address@hidden> wrote:

>Hi,
>
>Update, I manually changed the bcc.mk to CCexe_LDFLAGS := -Lobjs
>It still results in the same error. I don't get it, it seems like the
>current directory is changed ?
>
>bcc32 -A  -I.\objs -I.\builds\win32 -I.\include -c -q -y -d -v -Od -w-par
>-w-ccc -w-rch -w-pro -w-aus -DFT2_BUILD_LIBRARY
>-DFT_CONFIG_MODULES_H="<ftmodule.h>"  -I.\src\psnames -oobjs\psnames.obj
>.\src\psnames\psmodule.c
>.\src\psnames\psmodule.c:
>bcc32  -Lobjs -oobjs/apinames.exe 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
>Fatal: Unable to open file 'APINAMES.OBJ'
>mingw32-make: *** [objs/apinames.exe] Error 1
>Regards,
>Mirco
>
>2009/7/13 Mirco Babin <address@hidden>
>
>> 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 be replaced with -Lobjs
>>
>>  bcc32 -A  -I.\objs -I.\builds\win32 -I.\include -c -q -y -d -v -Od -w-par
>> -w-ccc -w-rch -w-pro -w-aus -DFT2_BUILD_LIBRARY
>> -DFT_CONFIG_MODULES_H="<ftmodule.h>"  -I.\src\psnames -oobjs\psnames.obj
>> .\src\psnames\psmodule.c
>> .\src\psnames\psmodule.c:
>> bcc32  -L./objs -oobjs/apinames.exe 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
>> Fatal: Unable to open file 'APINAMES.OBJ'
>> mingw32-make: *** [objs/apinames.exe] Error 1
>>
>> Regards,
>> Mirco
>>
>> 2009/7/10 <address@hidden>
>>
>> Hi,
>>>
>>> Could you try following patch? It fixes:
>>>
>>> * declare the suffix ".exe" to be added to "apinames".
>>> * prepare CCexe_CFLAGS & CCexe_LDFLAGS.
>>> * put "-Lobj" to CCexe_LDFLAGS when we use bcc.
>>>
>>> Regards,
>>> mpsuzuki
>>>
>>> diff --git a/builds/win32/win32-def.mk b/builds/win32/win32-def.mk
>>> index a82b146..e6ae31c 100644
>>> --- a/builds/win32/win32-def.mk
>>> +++ b/builds/win32/win32-def.mk
>>> @@ -22,6 +22,7 @@ PLATFORM  := win32
>>>  # The executable file extension (for tools). NOTE: WE INCLUDE THE DOT
>>> HERE !!
>>>  #
>>>  E := .exe
>>> +E_BUILD := .exe
>>>
>>>
>>>  # The directory where all library files are placed.
>>>
>>>
>>> diff --git a/builds/exports.mk b/builds/exports.mk
>>> index 5452b35..d84a4c2 100644
>>> --- a/builds/exports.mk
>>> +++ b/builds/exports.mk
>>> @@ -51,7 +51,7 @@ ifneq ($(EXPORTS_LIST),)
>>>   APINAMES_EXE := $(OBJ_DIR)/apinames$(E_BUILD)
>>>
>>>   $(APINAMES_EXE): $(APINAMES_SRC)
>>> -         $(CCexe) $(TE)$@ $<
>>> +         $(CCexe) $(CCexe_CFLAGS) $(CCexe_LDFLAGS) $(TE)$@ $<
>>>
>>>   .PHONY: symbols_list
>>>
>>> diff --git a/builds/compiler/bcc.mk b/builds/compiler/bcc.mk
>>> index 509cb72..c28359a 100644
>>> --- a/builds/compiler/bcc.mk
>>> +++ b/builds/compiler/bcc.mk
>>> @@ -75,4 +75,8 @@ CLEAN_LIBRARY ?= $(DELETE) $(subst
>>> /,$(SEP),$(PROJECT_LIBRARY))
>>>  LINK_LIBRARY   = tlib /u $(subst /,$(COMPILER_SEP),$@
>>> $(OBJECTS_LIST:%=+%))
>>>
>>>
>>> +# apinames linking
>>> +#
>>> +CCexe_LDFLAGS := -L$(OBJ_DIR)
>>> +
>>>  # EOF
>>>
>>>
>>>
>>>
>>> On Fri, 10 Jul 2009 15:44:56 +0200
>>> Mirco Babin <address@hidden> wrote:
>>>
>>> >Hi,
>>> >
>>> >The problem is that the linker can't find the OBJ file.
>>> >The current directory is .
>>> >The obj files are compiled into .\objs
>>> >From the current directory a link is performed, but the .\objs directory
>>> is
>>> >not set as a path.
>>> >
>>> >Indeed apinames.exe is just one obj.
>>> >
>>> >I'm looking forward to your solution, thanks in advance !
>>> >
>>> >Regards,
>>> >Mirco
>>> >
>>> >2009/7/10 suzuki toshiya <address@hidden>
>>> >
>>> >> Hi,
>>> >>
>>> >> Mirco Babin wrote (2009/07/10 21:53):
>>> >> > Well,
>>> >> >
>>> >> > I tried the following and it does not produce errors:
>>> >> > bcc32 -Lobjs -oobjs/apinames.exe src/tools/apinames.c
>>> >> >
>>> >> > The -L switch is to provide a library search path (where to find OBJ
>>> and
>>> >> LIB
>>> >> > files).
>>> >>
>>> >> Interesting. apinames.exe requires only apinames.c,
>>> >> no need to link other libraries and objects, so
>>> >> the requirement of "-Lobjs" is not easy to understand.
>>> >> Maybe we have to care the single command executing
>>> >> compilation and linking.
>>> >>
>>> >> > But I don't known what should be adjusted in the makefiles. They are
>>> >> really
>>> >> > complex.
>>> >>
>>> >> OK, I will take a look. Please wait 24 hours.
>>> >>
>>> >> Regards,
>>> >> mpsuzuki
>>> >>
>>> >> > Regards,
>>> >> > Mirco
>>> >> > 2009/7/10 suzuki toshiya <address@hidden>
>>> >> >
>>> >> >> 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
>>> >> >>> Fatal: Unable to open file 'APINAMES.OBJ'
>>> >> >>> mingw32-make: *** [objs/apinames] Error 1
>>> >> >>>
>>> >> >> I'm unfamiliar with bcc32 commandline syntax.
>>> >> >> How we can build "Hello World"-like program
>>> >> >> by bcc32? I think the author of the Makefile
>>> >> >> assumed that "bcc32 -ohello hello.c" is OK.
>>> >> >> Please let me know how to build hello world
>>> >> >> by bcc32.
>>> >> >>
>>> >> >> The command
>>> >> >>
>>> >> >> bcc32 -oobjs/apinames.exe src/tools/apinames.c
>>> >> >>
>>> >> >> can compile & link working executabe "apinames.exe"?
>>> >> >>
>>> >> >> Regards,
>>> >> >> mpsuzuki
>>> >> >>
>>> >> >
>>> >>
>>> >>
>>> >
>>>
>>
>>
>