> Do we have any plan of moving to cmake or other building systems or
> even autofool? ;)
cmake is a complexe c++ software, hence pulling a full c++
compiler/runtime into the "SDK" stack.
"autofool" is a set of ultra-complex perl5 and sh scripts... but at
least only a C compiler/runtime is required (some additionnal perl5
modules are required, but compile fine using C AFAIR).
For projects with unsignificant compile time, I would go a simple
sh script (see https://code.google.com/p/charfbuzz where I
stealfully inspired myself from ffmpeg configuration script).
For a project with a significant compile time, I would go for a
simple sh configure script, with a verbose and simple set of
makefiles (like before I would recommend to have a look at
ffmpeg).
Of course, those with "gcc -Ofast" will say compile time is most
of the time significant, those with "tinycc" will say compile
time is most of time neglictible...
The idea is to keep the "SDK" dependency tree as lean as the
"compile" and "runtime" dependency tree.
Most of the time, it's better to loose some programming comfort
to remove complex/big dependencies (... and you all know the
trend is the exact opposite: for little added comfort, huge and
complex dependencies are added).
my 2c.
--
Sylvain
No comments:
Post a Comment