"John Utz" <[EMAIL PROTECTED]> writes: > did you check *all* of your work into cvs? i tried to build out of > cvs today at about 2pm Pacific Standard Time and CVS was still > looking mighty 1.5.2-ish, so it wont do me any good to not have all > of it there....
Yeah, it was the first commit of the 1.6 stuff, so it has everything. I hadn't realized that anyone had actually ever checked out the code from CVS... > > http://xml.apache.org/dist/xerces-p/experimental/ > > > > I haven't bumped the version number since last time, but it is new. > > that's ok, the tarball will be my fallback if i cant build the cvs stuff. > > generally, i've been working out of the xml-xerces tree since december for > both java and c++ because i've been pushing the envelope pretty hard with > both flavors. That's excellent. It's very useful to have people actually developing code, I hope you'll be able to add your example to the list of sample apps. There are almost guaranteed to be features still missing. I am willing to add things as you need them, but you can do it as well. The trick is to look into the Xerces.i file (the SWIG interface module) and see what header files I list after a %include directive. Those are the files that SWIG is wrapping, if you need a class that is defined in a header file that I don't currently include, you can just add another %include (and an #include at the top - those show up in the Xerces.C %file). Then re-run make, and SWIG should kick in to re-create Xerces.pm and Xerces.C for you. In order for that to work, however, you must have run 'perl Makefile.PL' with the XERCES_DEVEL environment variable set. If this is too daunting, I can help. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
