On Wed, Dec 06, 2000 at 08:44:41PM +0100, Kaiserovi wrote:
> David,
>
> I find this discussion somehat irrelevant since expat 1.95 has solved
> this problem completely.
If that's the case, then things may be fine - but the current state of
the website is that there is a package for Expat provided - That
package is called 'Sablot-Expat-1.1.2.tar.gz'. The filename itself
seems to identify itself as a custom package of Expat for use with
Sablotron. Aside from the filename, the Expat sources have been
moved down a directory level, and the containing directory changed
from 'expat' to 'distribution'. Without spending a lot of time
examining things, one can't easily know what other changes may exist.
I don't see any references to expat 1.95 in the packaged instructions -
perhaps they're only available in CVS at this point.
> The way Sablotron used expat was the best one
> we could find, especially as we did not use autoconf at the beginning.
> Also, we needed a shared library version of expat, which is something
> you don't get from the original makefile. The structure of expat was
> left intact in the modified distribution, except for removed Windows
> binaries and the added makefiles.
That would have been clearest if the directory name had not been changed.
It wouldn't have been too much harder to either provide patches, or
write makefiles that used a standard source tree. Writing build scripts
that look for sources for an external library in a subdir of your
own sources...
So I tried to build Sablotron, failed, and gave up. I thought I'd drop
a note about the confusing situation, but I can't seem to get the point
across, so I'll give up on this too.
--
David Maxwell, [EMAIL PROTECTED]|[EMAIL PROTECTED] -->
Any sufficiently advanced Common Sense will seem like magic...
- me
