Well you need a static library if you want to link to it statically. The
standard binary builds of Xerces is a runtime library. You'll have to
download the source and build the staticlibrary yourself. Someone (I do not
remember who) on this list did some work a while ago to simplify building
Xerces as a static library.
So download the source and check it out.

I had alredy done all that work on our platform. It is very straightforward
to build a staticlibrary. Just compile each cpp file with the correct
parameters and then link all the object files together to a libray. It's is
like it was designed to be scripted isn't it? :)
Combined with funtion level linking you will end up with the smallest binary
image you can get because only those functions that you actually use is
linked in from Xerces.

Regards

Erik Rydgren
Mandarinen systems AB
Sweden


-----Original Message-----
From: Adam Lee [mailto:[EMAIL PROTECTED]
Sent: den 3 april 2003 00:26
To: Xerces_List (E-mail)
Subject: xerces shared lib size


hi,

We are trying to use part of the xerce lib functions in a resource
constrained embedded PC. We have encountered a problem that we don't really
have enough space to put the whole xerce library on the embedded PC. 

I tried to use -static flag in gcc in order to link to xerce lib statically
(i.e. can independently run without the presence of the lib file) but it
doesn't seem to do what I was expecting.

Any suggestions? i.e. how to link to it statically or compile a static
version of xerce lib or is there a more compacted version?

Thank you,
Adam
--------------
Adam Lee
Teletronics Technology Corporation
2525 Pearl Buck Road.
Bristol, PA 19007
TEL: (215) 785-2270 ext 157
Email: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

<<attachment: winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to