David Bertoni wrote:
Why not do:
runConfigure -p cygwin -c gcc -x g++ --prefix=/usr
> then do a make install, like similar autoconf-built packages?  I would
> recommend /usr/local instead of /usr, but that's really up to you.

Because I'm ignorant ;) Thanks a lot - the option for the runConfigure script is -P /usr/local btw - which is then passed on as --prefix=/usr/local

And whoop-de-doo - it's working! :)
I had to read a couple of error messages first, however, to recall that "make install" requires a preceeding "make" usually :)

$ XERCESCROOT=/home/lars/xerces-c-src_2_8_0
$ export XERCESCROOT
$ make clean
$ runConfigure -p cygwin -c gcc -x g++ -P /usr/local
$ make
$ make install

Et voilá!
-> /usr/local/include has the include directory xercesc
-> /usr/local/lib has the libraries
-> /usr/local/bin has the windows-dlls

Only downside is, for the execution of the windows-application built with gnu, I still need to manually copy the dll-files into c:\windows\system32 - is there a way to tell make install to use that directory as target for the binaries?

The Cygwin binaries are built to be run within the Cygwin environment, so the environment takes care of the symlinks, etc. If you really want to run Xerces-C binaries outside of Cygwin, you might try using Mingw, or just using the free version of Visual Studio.

I'm not sure I understand - what I am doing right now, with the .dll-files in windows' system32 folder, and compiling my application with the gnu toolchain, seems to be working fine (alternatively, having the .dll-files in the program directory, everything's working just as fine). At the end of the day, all I need to port my application to another windows system, is to copy the application executable & the required DLLs to the target folder, and run it from there.

All problems concerning the implementation of Xerces on my development computer solved! :) Look forward to questions incoming about the actual USE of Xerces-C from someone who has only done XML parsing under PHP with domxml before... *g*

Best Regards,

   Lars

Reply via email to