Re: [q-lang-users] Good news, everyone!

[Albert G. <Dr....@t-...>]

John Cowan wrote:
> Chicken is migrating to CMake, and in fact no longer supports autotools
> for Windows builds (except Cygwin, which can go either way).  CMake is
> also capable of generating Microsoft Visual C++ projects, which is a
> nice feature.  CMake also works fine on Unixoid systems.

I've taken a look at cmake quite a while ago, but the only thing that I
can remember is that at that time cmake wasn't capable enough to handle
all of Q's build requirements.

Can current cmake versions check for certain libc features? Most of Q's
autoconf deals with the incompatibilities in some parts of the system
interface. Another critical requirement is the ability to handle the
horrible complexities of cross-platform shared library handling, how
does cmake deal with this?

> CMake is also considerably faster, because it figures out only what
> the application need to figure out and then only once.  The current Q
> autotools build is horribly slow because there are so many "./configure"
> runs, all of which essentially discover the same thing.

Yes, that's because for modularity the various subpackages which come
bundled with Q have their own autoconf, and AFAICT there's no way to
make a sub-configure use the cache of the main package.

Albert

-- 
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikinformatik.uni-mainz.de/ag