Hi Christian, You made a good point about maintenance. I've updated the CMake build script which is available at https://github.com/vitaut/gecode/blob/master/CMakeLists.txt as before. The new version extracts all the source file names from Makefile.in and a substantial portion of the config header from config/support/config.h.in.
Best regards, Victor On Sat, Feb 2, 2013 at 12:08 PM, Christian Schulte <[email protected]> wrote: > Hi Victor,**** > > ** ** > > Thanks. The problem with this is that it’ll be difficult for us to keep > this up-to-date. If you had something that generates most of the script > that would be much more realistic to maintain (like automatically > extracting the files, etc).**** > > ** ** > > Any chance?**** > > ** ** > > Best and thanks a lot for the effort!**** > > Christian**** > > ** ** > > --**** > > Christian Schulte, www.ict.kth.se/~cschulte**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *[email protected] > *Sent:* Friday, February 1, 2013 11:57 PM > *To:* [email protected] > *Subject:* [gecode-users] CMake build script for Gecode**** > > ** ** > > Hi All,**** > > ** ** > > I've implemented a CMake <http://www.cmake.org/> build script for Gecode > which is available at > https://github.com/vitaut/gecode/blob/master/CMakeLists.txt . It's just a > single file that needs to be put in the top-level Gecode directory.**** > > ** ** > > I've ported most of the autoconf platform checks to CMake. Out-of-tree > builds and tests are supported. I've tested the script on Linux and MacOS X > with gcc and on Windows with Visual C++ (both nmake and Visual Studio > builds work).**** > > ** ** > > Hope it might be useful to someone.**** > > ** ** > > Best regards,**** > > Victor**** >
_______________________________________________ Gecode users mailing list [email protected] https://www.gecode.org/mailman/listinfo/gecode-users
