[tsc-devel] More on dependencies

Marvin Gülker | Sat, 14 Oct 2017 21:07:37 UTC

Hi everyone,

apart from the base library for which I started the other thread, there
are going to be some other dependencies. I try to keep the list as small
as reasonably possible.--

1. For XML, I suggest to use Xerces-C++[1]. Reason: It has a C++
interface (unlike libxml2), but it does not depend on glib (like
libxml++). glib is difficult on Windows experience shows. It has no
further hard dependencies, but optionally depends on ICU.

2. For scripting, we'll continue to use mruby, which has some build
dependencies that we can safely ignore, because absolutely normal
software (like bison). No runtime dependencies.

3. Gettext. This is required for translation support. As a standard
solution for i18n, I don't expect any problems with it; it's runtime
library has no dependencies if I remember correctly. On the first
glance, it looks as if its licenced GPL, with the implications everyone
knows. TSC currently uses it.

4. Tinyclipboard[2], my clipboard access library. SFML includes clipboard
support only starting with version 2.5[3], which is not released yet and
will take time to merge into normal distros. It has no further
dependencies other than the respective OS core libraries (libx11 on
Linux). It is built as part of TSC, so no external dependency is
created. TSC currently uses it.

Notably *not* in this list are:

* CEGUI and its plethora of subdependencies
* libxml++, which has build problems on Windows and depends on glib
* libpcre, as I think that TSC's scripting functionality does not need
  regular expressions.

Thoughts?

Marvin

[1]: http://xerces.apache.org/xerces-c/
[2]: https://www.guelkerdev.de/projects/tinyclipboard/
[3]: https://github.com/SFML/SFML/pull/1204

-- 
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F