Re: [Help-glpk] Help-glpk] [Fwd: CMAKE build environment (and version control)]

[Alpar Juttner]

Hi,

> I would like to note that glpk is part of the GNU project, so it is
> constrained to follow the GNU coding standards, where using GNU
> autotools is essential requirement

Not really. The related part of the GNU Coding Standards[1] only
requires a configure script with a given minimal set of parameters. It
explicitly allows using different build systems:

        "Each GNU distribution should come with a shell script named
        configure. [...] Many packages implement it using GNU Autoconf
        (see Introduction in Autoconf) and/or GNU Automake (see
        Introduction in Automake), but you do not have to use these
        tools. You can implement it any way you like; for instance, by
        making configure be a wrapper around a completely different
        configuration system.

So, CMAKE perfectly fits this requirement assuming that a wrapper
configure script is written to it (but I bet nobody will ever use it).

I must add that there are _major_ GNU projects that do _not_ even
provide a configure script.

>  (in particular, it is important for
> down-stream maintainers who maintain glpk, for example, for GNU/Linux).

I'm afraid I must also disagree here. Packaging a CMAKE based project is
no more difficult than those using autotool. All the distros providing
KDE has managed to solve it.

Not to mention the Windows packagers - CMAKE will essentially transform
their task to something like

        cmake ..
        nmake 
        cpack
        

> However, if you post me a cmake makefile for glpk, I can include it in
> the glpk distribution.

Here you can find a patch adding them:

http://lemon.cs.elte.hu/hg/glpk-cmake/raw-rev/4c8956a7bdf4

Though it is still a preliminary version and needs some polishing. For
example the doc creation (make pdfdoc) is not very beautiful, and right
now it creates both static and shared lib's, I'm not sure they are both
necessary.

It would be nice if others could test it and comment. I'm happy to make
any adjustments upon request. It also contains a simple tool that
includes the hg revision number into the version string. This part is
useless (though doesn't hurt) if the code is not under hg.

>  I need some template, because all glpk makefiles
> are generated automatically on creating the tarball.

Hmmm. Being a cross platform build tool, CMAKE is actually pretty much a
replacement for this makefile generator generator. :)

Regards,
Alpar

[1]
http://www.gnu.org/prep/standards/html_node/Configuration.html#Configuration