Hi Justin, Justin Dearing <[EMAIL PROTECTED]> writes:
> I see no good deed goes unpunished. Indeed ;-). > Well what would it take to get binaries distributed? Is it simply a matter > of me providing zipped compiled binaries? Or would this require > modifications to an official build server? If its simply a matter of > me attaching binaries to a jira ticker, and requires no build changes > I'll do that. It is quite a bit more involved. We will need to build, package (headers, documentation, tests, etc.), test, and sign them as well as update the download page and all other pages where we mention these things. While none of this is undoable, I am wondering is these, arguably marginal, platforms are worth the effort. Plus, AFAIK, Cygwin provides pre-compiled binaries of Xerces-C++ as part of their distribution. I am wondering of Mingw does or is willing to do the same thing. > If its more complicated than that I would like to be involved in > making thos platforms official for Xerces-3. Yes, it will be much more natural to do this for 3.0.0. > For the other platforms bullet list, I think its a good idea to make > it a table listing both compiler and platform like the supported > platforms. For gcc 3.2, we can simply list "Most platforms that have > gcc 3.4 support." Does Forrest support macros via entities.dtd? If so > I will move that table there. It will be useful for xerces 3. I am not sure whether Forrest supports DTD or not, but I don't think we should make porting to Forrest a requirement for release of 3.0.0. Anyway, for now, let's minimize the amount of changes necessary to get the Cygwin/Mingw instructions online. Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
