At 11:15 AM 8/15/2001, Don Mastrovito wrote:
>Chris,
>
>Yes it can. I don't use that feature too often, having the IDE
>available. In the IDE, select "Project|Export Makefile" from the
>menu. I've pasted a copy of that makefile below. In a DOS box, set your
>path to xerces-c-src1_5_1\Projects\Win32\BCB5\Xerces-all\XercesLib. Then
>execute the command "make -B -fXercesLib.mak". I just tried this and it
>seems to work OK. I suppose the make file ought to be included in the
>build tree along with the project file.
>
>Good luck,
>Don
I'm not actually using it at this time, but I think people would appreciate
being able to build with it.
Here are the problems I noticed:
* The free compiler doesn't ship with Turbo Assembler (tasm32.exe), and the
compiler uses tasm for inline assembly, so the __asm block in
XMLPlatformUtils::compareAndSwap (Win32PlatformUtils.c) should not be
used. Perhaps another define for the command line build to fall to the
other side of the #if condition would be appropriate?
Users of the command line compiler don't get VCL.
* vcl.h from XercesLib.cpp is not included with the free compiler. I don't
think XercesLib.cpp is required at all for a non-VCL build, but if it is,
<windows.h> should be used instead of <vcl.h> and all the USExxx stuff
should be conditionally excluded
* vcl library problems with linking: Memmgr.Lib sysinit.obj aren't needed
in ALLOBJ if you aren't using vcl. Remove all the vcl stuff (everything)
LIBRARIES, PACKAGES, SPARELIBS
* I needed to change cp32mti.lib to cw32mti.lib (I think this is correct)
in ALLLIB
With these steps I produced a DLL.
A nice, but not required change would be the incorporation of the output
directory creation in the makefile.
Thanks for the makefile, again I think it would make a great addition to
the build.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
