Xerces C++ support in cygwin

Xerces C++ support in cygwin

[abraham]

Hello,

I've been able to get xerces c++ to build in cygwin and
have submitted a couple of patches to enable this.  I
don't know how soon these fixes will be available in a
"stable" release, but for those that really want to
give it a try, I've included some instructions below. 
This is not for the faint of heart.  I'd like to
encourage anyone else that is interested to review the
"samples" and "tests" directories and get those to
build and run.

Limitations:
1) Since this is a c++ dll, there are issues of binary
compatibility between releases of gcc and other tools. 
In other words, if you build xerces succesfully with
version 2.95.3 of gcc, it won't work to link it against
your application that is built with gcc 3.1.1 (as I've
found out).
2) I've only been able to get this to compile with gcc
2.95.2.  When I tried against 3.1.1, ld would stackdump
at the final link to create the dll.  I don't even know
if there is a gcc 3.x that has been certified to work
under cygwin anyway, although I'd like it to so that I
could use the standard c++ headers in my code :)

Getting xerces to build:
1) Create your cvs view of the xerces-c source tree
(see http://xml.apache.org/cvs.html, you want
xml-xerces, and the "c" directory of that module).
2) cd to the c/src/xercesc directory of the cvs view
3) type the following at the cygwin prompt:
> ./runConfigure -p cygwin -c gcc -x g++ -m inmem -n
socket -t native
4) then type "make"
5) after everything is finished building, type "make
install"

you should now be able to use xerces in your app
(remember to use -lxerces-c in your link, and also make
sure that /usr/local/bin is in your windows %PATH% when
you run your app)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo,

> Getting xerces to build:
> 1) Create your cvs view of the xerces-c source tree
> (see http://xml.apache.org/cvs.html , you want
> xml-xerces, and the "c" directory of that module).

Use at least: 'cvs -z 3 ...', that was my problem, they have
big textfiles in the source and it is very slow when using
no compression!


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo abraham,

> I've been able to get xerces c++ to build in cygwin

Great.  I tried it some months ago, it was not possible
to get it to compile.  Since that time I don't like the
xml.apache folks very much.

Now I thought, give it another try, but *they* make still
problems... I cannot check it out with CVS, too bad.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo abraham,


> Getting xerces to build:
> 1) Create your cvs view of the xerces-c source tree
> (see http://xml.apache.org/cvs.html , you want
> xml-xerces, and the "c" directory of that module).
> 2) cd to the c/src/xercesc directory of the cvs view
> 3) type the following at the cygwin prompt:
>> ./runConfigure -p cygwin -c gcc -x g++ -m inmem -n
> socket -t native

What about threads: ' -r pthread '?


> 4) then type "make"
> 5) after everything is finished building, type "make
> install"

> you should now be able to use xerces in your app
> (remember to use -lxerces-c in your link, and also make
> sure that /usr/local/bin is in your windows %PATH% when
> you run your app)


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo Abraham,

> I've been able to get xerces c++ to build in cygwin and
> have submitted a couple of patches to enable this.


#=============== CygWin SPECIFIC OPTIONS =========================
ifeq (${PLATFORM}, CYGWIN)
   PLATFORM_COMPILE_OPTIONS = \
           -D__${PLATFORM}__ \            <---------- This is
           -I/usr/include \               <---------- really not
           -I/usr/include/w32api          <---------- neccessary
   MAKE_SHARED = ${CXX} -shared ${LDFLAGS}
   MAKE_SHARED_C = ${CC} -shared ${LDFLAGS}
   ifeq (${TRANSCODER}, ICU)
           ALLLIBS = ${LIBS} -L/usr/lib -L/usr/local/lib -L/usr/ccs/lib -licu-uc -licudata -lc
   else
           ALLLIBS = ${LIBS} -L/usr/lib
   endif
   EXTRA_LINK_OPTIONS = \
           -Xlinker --warn-once \
           -Xlinker -Map -Xlinker $(XML_LIB_DIR)/${LIBNAME}${VER}.map \
           -Xlinker --output-def -Xlinker $(XML_LIB_DIR)/${LIBNAME}${VER}.def \
           -Xlinker --out-implib -Xlinker $(XML_LIB_DIR)/${LIBNAME}${VER}.lib

Cygwin import libs should have the suffix '.dll.a' not '.lib'

      SHLIBSUFFIX=.dll
endif


-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Abraham Backus]

Here are my exact steps.... I'm using the latest of cygwin and all the other
necessary packages available via cygwin setup (make, gcc, etc.)

> mkdir /cvs_projects
> cd /cvs_projects
> cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
> cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout
xml-xerces/c
--- takes a long while ---
> cd xml-xerces/c/src/xercesc
> ./runConfigure -p cygwin -c gcc -x g++ -m inmem -n socket -t native
--- takes a little while ---
> make
--- takes a long while, and the last steps takes quite awhile and sucks up
memory as it links the xerces dll ---
> make install
--- takes a little while ---


It should work for you... a few people have added some patches (see
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6467 ).  I even completely
wiped out my cvs view and re-downloaded it via cvs checkout.

Note that I've also discovered that "./runConfigure -pcygwin -cgcc -xg++"
also works... the rest of the options are the same as the defaults for
cygwin that are in the runConfigure script.

An update on my problems with the tests and samples though:
I was able to update a few files to add cygwin support for these
directories, if you want to try them, download the two patch files attached
to "Xerces-C++ bug #12004 Samples/Tests don't build under cygwin"
( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12004 ).  With these
patches, just do "./runConfigure -pcygwin -cgcc -xg++" in both the
xml-xerces/c/tests and xml-xerces/c/samples directories.  Remember that
libxerces-c.dll must have been already built and installed prior to building
the tests and samples.

Now the tests and samples build ok, but when I try to run the tests, I get a
stackdump.  It appears that either gcc or cygwin has a problem with c++
exceptions being thrown from a dll.  I stepped through the DOMMemTest app in
gdb and it puked at about the moment where a DOMException would be thrown.
I've seen some mention of this c++ exceptions problem in the cygwin mailing
list archives, but don't see any solutions or further ideas about where the
problem lies, although I thought I saw mention somewhere that the problem
exists in other platforms besides cygwin when gcc is used.

-Abe

----- Original Message -----
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: <cygwin@cygwin.com>
Sent: Saturday, August 24, 2002 6:18 PM
Subject: Re: Xerces C++ support in cygwin


> Hallo abraham,
>
>
> > Getting xerces to build:
> > 1) Create your cvs view of the xerces-c source tree
> > (see http://xml.apache.org/cvs.html , you want
> > xml-xerces, and the "c" directory of that module).
> > 2) cd to the c/src/xercesc directory of the cvs view
> > 3) type the following at the cygwin prompt:
> >> ./runConfigure -p cygwin -c gcc -x g++ -m inmem -n
> > socket -t native
>
> What about threads: ' -r pthread '?
>
>
> > 4) then type "make"
> > 5) after everything is finished building, type "make
> > install"
>
> > you should now be able to use xerces in your app
> > (remember to use -lxerces-c in your link, and also make
> > sure that /usr/local/bin is in your windows %PATH% when
> > you run your app)
>
>
> Gerrit
> --
> =^..^=
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Abraham Backus]

Awesome!  I'm kinda new about what's expected of cygwin software with regard
to what files are needed where.  I discovered though that after everything
is built, if I put libxerces.dll into /usr/local/bin and then put a symlink
to it in /usr/local/lib that everything builds ok.  That seems odd and it
"worked" for my one test app that I've been working on, but it just didn't
seem right because any other dll that my apps link to seemed to have a
.dll.a file in the lib directory.

Thanks again!
-Abe

----- Original Message -----
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: <abraham@backus.com>
Cc: <cygwin@cygwin.com>
Sent: Saturday, August 24, 2002 6:39 PM
Subject: Re: Xerces C++ support in cygwin


> Hallo Abraham,
>
> > I've been able to get xerces c++ to build in cygwin and
> > have submitted a couple of patches to enable this.
>
>
> #=============== CygWin SPECIFIC OPTIONS =========================
> ifeq (${PLATFORM}, CYGWIN)
>    PLATFORM_COMPILE_OPTIONS = \
>            -D__${PLATFORM}__ \            <---------- This is
>            -I/usr/include \               <---------- really not
>            -I/usr/include/w32api          <---------- neccessary
>    MAKE_SHARED = ${CXX} -shared ${LDFLAGS}
>    MAKE_SHARED_C = ${CC} -shared ${LDFLAGS}
>    ifeq (${TRANSCODER}, ICU)
>            ALLLIBS =
${LIBS} -L/usr/lib -L/usr/local/lib -L/usr/ccs/lib -licu-uc -licudata -lc
>    else
>            ALLLIBS = ${LIBS} -L/usr/lib
>    endif
>    EXTRA_LINK_OPTIONS = \
>            -Xlinker --warn-once \
>            -Xlinker -Map -Xlinker $(XML_LIB_DIR)/${LIBNAME}${VER}.map \
>            -Xlinker --output-def -Xlinker
$(XML_LIB_DIR)/${LIBNAME}${VER}.def \
>            -Xlinker --out-implib -Xlinker
$(XML_LIB_DIR)/${LIBNAME}${VER}.lib
>
> Cygwin import libs should have the suffix '.dll.a' not '.lib'
>
>       SHLIBSUFFIX=.dll
> endif
>
>
> --
> =^..^=
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo Abraham,

> Now the tests and samples build ok, but when I try to run the tests, I get a
> stackdump.  It appears that either gcc or cygwin has a problem with c++
> exceptions being thrown from a dll.  I stepped through the DOMMemTest app in
> gdb and it puked at about the moment where a DOMException would be thrown.
> I've seen some mention of this c++ exceptions problem in the cygwin mailing
> list archives, but don't see any solutions or further ideas about where the
> problem lies, although I thought I saw mention somewhere that the problem
> exists in other platforms besides cygwin when gcc is used.

I remember, I got this problem too when I got it it to compile the
first time (some assert statement).  Doesn't this happen in the DLL, and
therefore affects all executables linked against it?


Gerrit
-- 
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo Abraham,

Am Sonntag, 25. August 2002 um 06:47 schriebst du:

> Awesome!  I'm kinda new about what's expected of cygwin software with regard
> to what files are needed where.  I discovered though that after everything
> is built, if I put libxerces.dll into /usr/local/bin and then put a symlink
> to it in /usr/local/lib that everything builds ok.  That seems odd and it
> "worked" for my one test app that I've been working on, but it just didn't
> seem right because any other dll that my apps link to seemed to have a
> .dll.a file in the lib directory.

This part is wrong:

ifeq (${PLATFORM}, CYGWIN)
        -mkdir -p ${PREFIX}/bin
        $(CP) ${FQ_LINK_NAME} ${PREFIX}/bin
        rm -rf ${PREFIX}/lib/${LINK_NAME} && \
        ln -s ${PREFIX}/bin/${LINK_NAME} ${PREFIX}/lib/${LINK_NAME}
else

You cannot 'ln -s' a DLL on windows.
Also the DLL's don't need to be renamed.
Just put the created DLL (libxerces-c2_1_0.dll) into ${PREFIX}/bin.
And then put the import library (libxerces-c2_1_0.dll.a) into
${PREFIX}/lib, you can 'ln -s' now the import library:
ln -s ${PREFIX}/lib/libxerces-c2_1_0.dll.a ${PREFIX}/lib/libxerces-c.dll.a
ln -s ${PREFIX}/lib/libxerces-c2_1_0.dll.a ${PREFIX}/lib/libxerces.dll.a


The patch looks like this then:
===============================
--- Xerces/c/obj/Makefile.in~   2002-08-25 16:34:12.000000000 +0200
+++ Xerces/c/obj/Makefile.in    2002-08-25 16:52:11.000000000 +0200
@@ -92,6 +92,10 @@
 else
 LIBNAME=libxercesc
 endif
+ifeq (${PLATFORM}, CYGWIN)
+LIBNAME=libxerces-c
+IMPORTLIB=libxerces-c
+endif
 
 ALL_OBJECTS=$(wildcard $(PLATFORM)/*.o)
 
@@ -145,6 +149,7 @@
 # link your application.                               #
 ########################################################
 
+ifneq (${PLATFORM}, CYGWIN)
 ${FQ_REAL_NAME}:       $(ALL_OBJECTS)
        @echo Building ${FQ_REAL_NAME}
        ${MAKE_SHARED} ${LD_SONAME} -o ${@} ${^} $(TEMPLATESOBJS) $(PLATFORM_LIBRARIES) $(EXTRA_LINK_OPTIONS) $(ALLLIBS)
@@ -152,6 +157,11 @@
        rm -rf ${FQ_SO_NAME}   && ln -s ${FQ_REAL_NAME} ${FQ_SO_NAME}
        @echo symlink ${FQ_LINK_NAME}
        rm -rf ${FQ_LINK_NAME} && ln -s ${FQ_SO_NAME} ${FQ_LINK_NAME}
+else
+${FQ_REAL_NAME}:       $(ALL_OBJECTS)
+       @echo Building ${FQ_REAL_NAME}
+       ${MAKE_SHARED} ${LD_SONAME} -o ${@} ${^} $(TEMPLATESOBJS) $(PLATFORM_LIBRARIES) $(EXTRA_LINK_OPTIONS) $(ALLLIBS)
+endif
 
 ## Start OS390 ##
 ifeq (${PLATFORM},OS390)
@@ -194,9 +204,11 @@
        -mkdir -p ${PREFIX}/lib
 ifeq (${PLATFORM}, CYGWIN)
        -mkdir -p ${PREFIX}/bin
-       $(CP) ${FQ_LINK_NAME} ${PREFIX}/bin
-       rm -rf ${PREFIX}/lib/${LINK_NAME} && \
-       ln -s ${PREFIX}/bin/${LINK_NAME} ${PREFIX}/lib/${LINK_NAME}
+       $(CP) ${FQ_REAL_NAME} $(PREFIX)/bin
+       $(CP) ${XML_LIB_DIR}/${IMPORTLIB}${VER}.dll.a $(PREFIX)/lib
+       rm -rf ${PREFIX}/lib/${IMPORTLIB}.dll.a ${PREFIX}/lib/libxerces.dll.a
+       ln -s ${PREFIX}/lib/${IMPORTLIB}${VER}.dll.a ${PREFIX}/lib/${IMPORTLIB}.dll.a
+       ln -s ${PREFIX}/lib/${IMPORTLIB}${VER}.dll.a ${PREFIX}/lib/libxerces.dll.a
 else
        $(CP) ${FQ_REAL_NAME} $(PREFIX)/lib
 endif


# END PATCH

If you link your app with -lxerces, the linker will pick up
${PREFIX}/lib/libxerces.dll.a automatically then.

Do you want to test it and commit it to the Xerces developers?


Gerrit
-- 
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Abraham Backus]

I've tested Gerrit's patch and submitted it (among others to get more
support for cygwin in Xerces-C++).  These patches were checked in today and
I just finished testing using gcc 3.2.1 that was recently announced.  Feel
free anyone to get the sources from cvs and build it...  Great news is that
with gcc 3.2.1, I'm seeing the C++ DOM exceptions being caught when they are
thrown from the xerces dll, which allows all the xerces tests to pass. (this
was a problem when I built the xerces dll and tried running the tests
against gcc 2.95.3).

I'd like to prep this for cygwin packaging ( http://cygwin.com/setup.html )
and would welcome any feedback regarding the issues surrounding gcc versions
(or any other issues that anyone would see).  As I understand it (and
experienced), since this is a dll that exposes c++ types, that if the dll is
compiled using one version of gcc, you won't be able to link against it with
another version of gcc.  I haven't delved into this, but I assume that
someone knows if a dll built using any 2.x version of gcc can be linked
against any other code built using a different  2.x version of gcc?  In
other words, does someone know at which version number level does binary
compatibility break?

thanks!
-Abe


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Hallo Abraham,

Am Montag, 26. August 2002 um 22:22 schriebst du:

> I've tested Gerrit's patch and submitted it (among others to get more
> support for cygwin in Xerces-C++).  These patches were checked in today and
> I just finished testing using gcc 3.2.1 that was recently announced.  Feel
> free anyone to get the sources from cvs and build it...  Great news is that
> with gcc 3.2.1, I'm seeing the C++ DOM exceptions being caught when they are
> thrown from the xerces dll, which allows all the xerces tests to pass. (this
> was a problem when I built the xerces dll and tried running the tests
> against gcc 2.95.3).

Have you also tried to build and test with threads?  It seems to build
ok for me, but I have no time left to test it yet, I'll do tests this
evening.

And what about Xalan?


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Abraham Backus]

Yes, I've been calling runConfigure like so:
> ./runConfigure -pcygwin -cgcc -xg++

The runConfigure script defaults to pthread for the thread option, so that's
enabled.
One of the tests "ThreadTest", I assume does multi-threaded testing and it
passes when I ran it.  It took a little effort to figure out how the tests
are run because a few of them require arguments and file names.  I walked
through the scripts/sanityTest.pl script and executed the tests as they are
in that file.  I wasn't able to run the script itself, which is another
thing on the checklist :)

I haven't even tried Xalan.

----- Original Message -----
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: <cygwin@cygwin.com>
Sent: Monday, August 26, 2002 11:50 PM
Subject: Re: Xerces C++ support in cygwin


> Hallo Abraham,
>
> Am Montag, 26. August 2002 um 22:22 schriebst du:
>
> > I've tested Gerrit's patch and submitted it (among others to get more
> > support for cygwin in Xerces-C++).  These patches were checked in today
and
> > I just finished testing using gcc 3.2.1 that was recently announced.
Feel
> > free anyone to get the sources from cvs and build it...  Great news is
that
> > with gcc 3.2.1, I'm seeing the C++ DOM exceptions being caught when they
are
> > thrown from the xerces dll, which allows all the xerces tests to pass.
(this
> > was a problem when I built the xerces dll and tried running the tests
> > against gcc 2.95.3).
>
> Have you also tried to build and test with threads?  It seems to build
> ok for me, but I have no time left to test it yet, I'll do tests this
> evening.
>
> And what about Xalan?
>
>
> Gerrit
> --
> =^..^=
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Xerces C++ support in cygwin

[Gerrit P. Haase]

Abraham schrieb:

> I walked through the scripts/sanityTest.pl script and executed the tests as
> they are in that file.  I wasn't able to run the script itself, which is
> another thing on the checklist :)

Hmm, problems with perl?

>> And what about Xalan?

> I haven't even tried Xalan.

Then I'll take a look at Xalan.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/