(apologies if this is duplicated; I sent from the wrong address before)

I have about 70% of an XML parser done that I haven’t gotten around to 
finishing yet. Once that’s completed, we don’t need libxml. I can’t remember if 
we need iconv; it’s used for character set conversions but DocFormats is UTF-8 
native (as is libxml), and support for UTF-16 would not be hard (if it’s even 
needed).

I would strongly argue against keeping sources of libraries in our repositories 
except in the case where we have made changes to those libraries. If we do that 
we have to include all of SDL_image and thus all of SDL, and that leads to 
quite a big repository. The same goes for libz etc. Most projects have lots and 
lots of dependencies and are handled just fine by standard package dependency 
systems e.g. apt-get.

Furthermore, we want to use the system libxml where available, both to take 
advantage of shared libraries (libxml only needs to exist in memory once, the 
OS maps it into the address space of each process that uses it), and for 
security updates (system libxml updated due to vulnerability, programs using 
DocFormats are still vulnerable until we go and update our own version).

—
Dr Peter M. Kelly
[email protected]

PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key>
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)

> On 23 Mar 2015, at 3:29 pm, jan i <[email protected]> wrote:
> 
> Hi.
> 
> I am nearly finished with the x64 port for windows, I have compiled all
> libraries we need.
> 
> I wanted to see if we could keep the library sources in our Repo, and
> integrate them in our build
> system, as it would simplify things. Since I am biased I asked on
> [email protected] to get the opinion
> of outside Mentors. I got a few responses (strangely enough all in
> private), and it turns out many projects do as I suggest.
> 
> However one of the others mentors found a license problem with iconv. We do
> not use iconv, but by default libxml2 does. I can configure libxml2 not to
> include iconv, but I wanted to ask in here, if we need the functionality ?
> 
> If not my plan has changed a bit, and I will include the sources in
> platform, make a single commit with each original source, noting the URL
> and version in the commit text (and add it to LICENSE). Then I will add my
> changes, which will be solely CMAKE files NO source changes.
> 
> Having the source in our build system, will also allow us to decide how to
> handle other platforms.
> 
> Rgds
> jan I.

Reply via email to