James Berry wrote:
> I've been working on the branch https://svn.apache.org/repos/asf/
> xerces/c/branches/jberry/3.0-unstable on a first cut at autoconf
> support and cross-platform reorganization for Xerces 3.0.
>
> It's now at a point where I've love to get a couple of other eyes on
> it before I commit to (hah, hah) committing it to the main Xerces 3.0
> trunk.
>
> Highlights at present:
>
>      - It now builds on Mac OS X and Freebsd (on one box, anyway).
>      - Support for icu, iconv, and Mac OS transcoders.
>      - Support for sockets and macos netacessors.
>      - Support for inmemory message loader.
>      - Configure/build is through ./configure && make
>
>      - PlatformUtils refactored into finer chunks. Addition of new:
>      - AtomicOpManagers (Mac OS, Mutex-protected, NoThread)
>      - MutexManagers (Posix pthreads, NoThread)
>      - FileMangagers (Posix only at present)
>
> Could one or several of you look it over and give feedback on this
> before I merge to the main trunk? I want to make sure I haven't gone
> completely astray.

Hi James,

great work! For me it seems like a reasonable framework, and it should be 
rather easy to plug support for other platforms.

I have started to add linux support for autoconf. And got it through 
after two hours only :)

However, here's an issue with the links in the config directory - on my 
system, the destination files are found at /usr/share/libtool, rather 
than at /opt/local/share/libtool. I have no idea about how to fix this 
in a platform- and distribution-independend way. My simple workaround, 
deleting the links and creating new ones to the right destination, 
surely would break e.g. your setup - so how could we fix this?

Cheers,
                        Axel

-- 
Humboldt-Universit�t zu Berlin
Institut f�r Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Wei�
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050
** www.freesp.de **

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to