Gareth wrote:
> Does anyone know if we do support solaris 10?
We've been playing with Solaris 10 here. Mostly ok.
There have been a couple of issues on the x86-64 platform:
* The 'configure' script doesn't like selecting 64-bit compiles
under x86-64 Solaris. IIRC, the default "runConfi
Hi James,
Not that I am arguing against but the templates use the define
XERCES_TMPLSINC (ie. #if !defined(XERCES_TMPLSINC)) to determine whether
or not to include the .c files. Inside src/xercesc/Makefile.incl for HPUX
if the compiler is not aCC then this define is set. I am not sure what
compi
James Berry <[EMAIL PROTECTED]> writes:
> On Feb 20, 2005, at 2:17 AM, Jason E. Stewart wrote:
>
> Maybe we'd like to clean house and get rid of the _d and Beta tags
> for the 1.x line? That seems like ancient history. We might also do
> something like move create a tags/releases directory to
As part of planning for the next major release of xerces-c, to take
place sometime this year, I'd like to get comment on the following.
Our current plan is to drop support for Mac OS prior to Mac OS X 10.1.
This means there will be no support for Mac OS 8 or 9 systems, running
either natively o
On Feb 20, 2005, at 7:16 AM, James Berry wrote:
Options:
(1) Get into a potentially long, drawn out debate with Xerces-j
about migrating the repositories.
(2) Migrate just xerces-c to svn, but leave the top-level
directory structure similar to what it is now to accommodate a
potential fu
On Feb 20, 2005, at 2:17 AM, Jason E. Stewart wrote:
Hey All,
Email #2 in my series...
The current ASF repos at:
https://svn.apache.org/repos/asf/
has all the TLP's as top-level projects. Since Xerces-C is officially
still part of XML and not it's own TLP (true??), we would go under
Gareth, can y
Hi Jason,
That's an interesting question. I'll try to suggest an equally
interesting answer.
Notes:
(1) There is no particular sharing of code, etc, between xerces-j
and xerces-c that I know of, so there would seem to be no particular
reason they need to share the same repository. Can anybo
Hey All,
Should we be involving the Xerces-J team in this discussion, since we
are scheduled to become one big happy TLP at some point?
Just a thought...
Cheers,
jas.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional c
Hey All,
Email #2 in my series...
The current ASF repos at:
https://svn.apache.org/repos/asf/
has all the TLP's as top-level projects. Since Xerces-C is officially
still part of XML and not it's own TLP (true??), we would go under
https://svn.apache.org/repos/asf/xml/xerces-c
The current
Hey all,
We definately want the trunk (HEAD) - what other tags/branches do we
want? The easiest is to simply dump everything - the pros of this is
that it is the simplest to do and then we can forget about the CVS
repository. The only con I can think of would be if the CVS archive
has some ugly st
James Berry <[EMAIL PROTECTED]> writes:
> I'm happy to help set a blackout date, but I think we need to get
> the migration spec together first, and get basic agreement on that,
> before setting such a date.
Hey James,
Sorry - I was getting ahead of myself.
I finally took the time to do the re
11 matches
Mail list logo
