[xml] RE: Compiling the xml library with Borland C++ Builder 6 under Windows XP

Bonjour Cyrille,

Yes, I see the problem. Your BCB compiler is installed in a location 
that has a space in the path name, and that is creating a problem
with parsing the -L compiler directive. I haven't experienced this 
problem, because on my setup, $(BCB) expands to the short form (e.g., 
c:\progra~1\borland\cbuild~1). I'm not sure why we see different 
behaviours, but there is an easy work-around. Just change the 
line in the Makefile that reads:

        LDFLAGS = $(LDFLAGS) -L$(BINDIR);$(LIBPREFIX);$(LIB);$(BCB)\lib\PSdk


        LDFLAGS = $(LDFLAGS) -L"$(BINDIR);$(LIBPREFIX);$(LIB);$(BCB)\lib\PSdk"

That is, put quotes around the full path list supplied with -L.

Let me know if that fixes the problem. If it works for you, I'll submit 
it as a patch.

One other thing to note: after running the configuration script, you
don't need to use

        make -f Makefile.bcb

The configuration script copies Makefile.bcb (or one of its siblings,
depending on the compiler you specify) to Makefile, so all you really
need is just:


Which will use Makefile by default.


Eric Zurcher
CSIRO Livestock Industries
Canberra, Australia
Eric Zurcher csiro au

-----Original Message-----

Message: 6
From: "Cyrille Gautard" <cyrille gautard wanadoo fr>
To: <xml gnome org>
Date: Tue, 23 Mar 2004 16:07:12 +0100
Subject: [xml] Compiling the xml library with Borland C++ 
Builder 6 under Windows XP

I try to compile the libxml2 library under Windows using the 
Borland C++
Builder 6 compiler. I follow the instructions and fist execute the
configure.js script by passing the arguments corresponding to 
Borland :
Cscript configure.js compiler=bcb prefix=c:\opt iconv=no debug=yes
Then I launch make -f Makefile.bcb
Here is the output : 
        ilink32.exe -q -U2.6 -Lbin.bcb;c:\opt\lib;.;C:\Program
Files\Borland\CBuilder6\lib\PSdk -Tpd -Gi c0d32.obj int.bcb\c14n.obj  
int.bcb\catalog.obj int.bcb\chvalid.obj  int.bcb\debugXML.obj  int.bcb\dict.obj
int.bcb\DOCBparser.obj int.bcb\encoding.obj  int.bcb\entities.obj  int.bcb\error.obj
int.bcb\globals.obj  int.bcb\hash.obj  int.bcb\HTMLparser.obj  int.bcb\HTMLtree.obj
int.bcb\legacy.obj  int.bcb\list.obj  int.bcb\nanoftp.obj  int.bcb\nanohttp.obj
int.bcb\parser.obj  int.bcb\parserInternals.obj  int.bcb\pattern.obj
int.bcb\relaxng.obj  int.bcb\SAX.obj  int.bcb\SAX2.obj  int.bcb\threads.obj  
int.bcb\tree.obj int.bcb\uri.obj  int.bcb\valid.obj  int.bcb\xinclude.obj  int.bcb\xlink.obj
int.bcb\xmlIO.obj  int.bcb\xmlmemory.obj  int.bcb\xmlreader.obj
int.bcb\xmlregexp.obj  int.bcb\xmlschemas.obj  int.bcb\xmlschemastypes.obj
int.bcb\xmlunicode.obj  int.bcb\xmlwriter.obj  int.bcb\xpath.obj  int.bcb\xpointer.obj
int.bcb\xmlstring.obj,bin.bcb\libxml2.dll,,import32.lib cw32mti.lib wsock32.lib
Fatal: Unable to open file 'PSDK.OBJ'
I have no ideas to explain why it fails on the linkage. Can 
you help me to solve this problem please?
Cyrille Gautard


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]