<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [CMake] Changing the default name "CMakeLists.txt"</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>>From a simple grep in the cmake CVS sources I think that to add such an option<BR>
>first would require to have a unified place with the "CMakeLists.txt" string<BR>
>value because currently there are about 15 different places in code where the<BR>
>string is hardcoded, about 30 places where it appears in messages generated<BR>
>from the code and A LOT of code comments and cmake module comments where it's<BR>
>used (tho the comments can be left in place since they still make sense<BR>
>talking about a CMakeLists.txt file even if that is configurable).<BR>
<BR>
All in all I don't think it's very hard to do it, would result in a better<BR>
cmake code organization too (not having scattered "CMakeLists.txt" magic<BR>
value all over the code).<BR>
<BR>
Sounds great! I will consider doing it!<BR>
The thing is that I am trying to make a sort of "unified" or "common build system" (cbs) for which I<BR>
use cmake. The idea was that open source projects could maintain such a cbs-makefile, which combined<BR>
with a set of common cmake files would make it very easy to to use 3rd party libraries within your own code.<BR>
<BR>
A short intro is on the very preliminary web page (cpaf.sourceforge.net) repeated here:<BR>
---------------------------------------------------------------<BR>
The cmake based build system along with associated python helper scripts have been factored out as a seperate project located in cpaf/cbs for now. The general idea is to supply a general and very simple way to produce a cbs/cmake file(s) for a project (e.g. a library) and then this library can build seamlessly together with other "cbs-enabled" libs/apps.<BR>
<BR>
In your top level directory of your own project you also keep a myprj.BuildConfig.cmake file which contains a use entry/line for every library you want to enable/use in your project like this:<BR>
<BR>
# --- 3RD PARTY LIBRARIES ---<BR>
SET ( z_USE SYSTEM ) # Use system installed version<BR>
SET ( png_USE BUILD ) # Build from local source code<BR>
SET ( bz2_USE DISABLED ) # Don't use this lib at all<BR>
SET ( boost_USE PREBUILT ) # Use allready locally (cbs) compiled version of boost.<BR>
<BR>
# Other build options<BR>
SET ( z_LINK_TYPE STATIC ) # Force static version of zlib even when cbmake.py -l shared is used. <BR>
<BR>
<BR>
<BR>
So the (perhaps naive) hope is that many open source SW projects will pick up the idea and provide cbs build files for their code. See the "CBS Introduction" page how simple it really is to use this system.<BR>
<BR>
--------------------------------------<BR>
<BR>
The reason I would like another default CMakeLists.txt name is that I don't want to conflict with projects using cmake allready for their build process.<BR>
--<BR>
<BR>
>Mihai RUSU Email: dizzy@roedu.net<BR>
> "Linux is obsolete" -- AST<BR>
>_______________________________________________<BR>
>CMake mailing list<BR>
>CMake@cmake.org<BR>
><A HREF="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>