Use case:
You start developing src/prototype1 which implements feature X. Next, you copy
src/prototype1 to src/prototype2 and implement feature Y or enhance feature X.
You don't branch because you're constantly comparing these prototypes against
each others (say for speed).
To make this really ea
> You may want to use custom CPack scripts for different purposes. By default,
> CPack uses script generated by CMake in top-level directory, but you can
> write your own one (and as many as you want) and pass it to cpack as command
> line parameter.
> Of course, install components could be great h
On Fri, January 30, 2009 14:37, Eric Noulard wrote:
> As far as I know CPack only handles a single per-project package,
> i.e. you may easilly build a package (deb, rpm, tgz etc...) for the WHOLE
> project, even if the project does have subdirectories.
> CPack will package all target, files etc...
Hello
I seem not able to find an example of how to generate .deb files with cpack for
different subdirectories of a project. Is this possible and if so, how?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On 03/19/2008 09:50 PM, Ken Martin wrote:
> Can you do the glob, configure the result out to a file, then INCLUDE
that
> file. I believe that will solve the problem. Something like
>
> file(GLOB SRC *.cpp)
> configure_file(somefile.in somefile)
> include(somefile)
>
> where somefile.in looks li
On 03/09/2008 09:18 AM, Sergey Nik wrote:
Hi all,
I'm looking information how I can determinate GCC version in my
CMakeLists.txt script.
After short searching mail list archive I've not found something relevant.
Is it possible?
Thank you in advance,
Sergey
A combination of EXECUTE_PROCESS a
I guess you missed my answer yesterday ...
If I'm not mistaken calling just cmake path_to_your_project_srcs doesn't set the
BUILD_TYPE to anything.
What about the following:
% cd build/your_project/debug;
% cmake path_to_project_srcs -DCMAKE_BUILD_TYPE=DEBUG
% cd build/your_project/release
% cm
On Tue, March 4, 2008 11:27, Malhotra, Anupam wrote:
> CMAKE_BUILD_TYPE is not initialized with a readable value at
> configuration time. This is because the user is free to select a build
> type at build time. Now in visual studio 6/visual studio 8 2005 we can
> select the build type by selecting
I guess the following would suit your needs too:
# AUX_SOURCE_DIRECTORY: Find all source files in a directory.
AUX_SOURCE_DIRECTORY(dir VARIABLE)
Collects the names of all the source files in the specified directory
and stores the list in the variable provided. This command is intended
to
On Mon, February 25, 2008 11:11, dizzy wrote:
> On Sunday 24 February 2008 23:22:58 blinkeye wrote:
>> >> On 2/24/08, David Sveningsson <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hi, I'm quite new with cmake and I can't figure out how to enable
&
>> On 2/24/08, David Sveningsson <[EMAIL PROTECTED]> wrote:
Hi, I'm quite new with cmake and I can't figure out how to enable
warnings for the generated makefiles/projects. For instance, I would
like to use the -Wall flag with gcc.
like that for example:
set( CMAKE_C_FLAGS "-fstack-protecto
On Fri, February 22, 2008 10:07, Bill Hoffman wrote:
> BlinkEye wrote:
>> On Thu, February 21, 2008 22:23, Alan W. Irwin wrote:
>>> On 2008-02-21 21:57+0100 blinkeye wrote:
>>>> [...]At the moment I'm just creating plain .so libs, without any version
>>
On Thu, February 21, 2008 22:23, Alan W. Irwin wrote:
> On 2008-02-21 21:57+0100 blinkeye wrote:
>
>> [...]At the moment I'm just creating plain .so libs, without any
>> version number (so far I didn't happen to come across a shared library
>> tutorial with cmake
Hi guys
I'm getting along very well (and quickly!) with porting two large
projects from Makefiles to CMake. Actually, 3 projects will follow later
on (and possibly more). Yeah, CMake is actually THAT great. I just
wanted to share my delight and acknowledgement of this tool, it makes
developin
On 02/17/2008 04:58 PM, Alexander Neundorf wrote:
On Sunday 17 February 2008, blinkeye wrote:
Hi guys
I'm in the process of replacing Makefiles from two large projects with
CMake files. So far it's working great, but now I hit a wall:
I need to generate .cpp and .h files from i
On 02/17/2008 04:51 PM, Mike Jackson wrote:
Lets assume for a second that your layout is something like:
Project
src
-sub1
--CMakeLists.txt
--sub1.cpp
--sub1.ui
-sub2
--CMakeLists.txt
--sub2.cpp
What you would want quite possible is a top level CMakeLis
On 09/21/2007 10:15 PM, Juan Sanchez wrote:
Hello,
How do you add an externally library for linking into a target? I am
getting something like this from TARGET_LINK_LIBRARIES?
CMake Error: Attempt to add link library "/bar/linux-x86/opt/foo.a" to
target "waterlooApps" which is not built by th
On 09/20/2007 09:18 PM, Bill Hoffman wrote:
...
That said, FILE(TO_CMAKE_PATH ...) should work just fine, please post
an example that does not work.
-Bill
On 09/20/2007 09:15 PM, Alexander Neundorf wrote:
>...
> I still don't see a FILE(TO_CMAKE_PATH ...) in the example.
>
> Alex
Hi guy
On 09/20/2007 09:00 PM, Bill Hoffman wrote:
BlinkEye wrote:
Thanks for the reply, but this doesn't work neither.
I wonder if I'm the only one who ran into what appears to be a very basic issue.
Basically, you are using cmake incorrectly. You should not be using
environment
On Thu, September 20, 2007 19:34, kitts wrote:
> On Tuesday 18 Sep 2007 10:31:25 pm blinkeye wrote:
>> >> I'm not able to convince cmake to properly use an environment variable
>> >> which consists of more than one entry for the INCLUDE_DIRECTORIES
>> >>
On Wed, September 19, 2007 14:32, Bill Hoffman wrote:
> Andreas Pakulat wrote:
>> Hi,
>>
>> yesterday I noticed that the Debug buildtype has the same problems as
>> the --enable-debug option in autohell. Its not possible to properly
>> debug an application that has been built with CMAKE_BUILD_TYPE=
On 09/18/2007 06:09 PM, Alexander Neundorf wrote:
On Tuesday 18 September 2007 11:35, BlinkEye wrote:
Hi guys
I'm not able to convince cmake to properly use an environment variable
which consists of more than one entry for the INCLUDE_DIRECTORIES
directive. It always takes the value as
Hi guys
I'm not able to convince cmake to properly use an environment variable which
consists of more than one entry for the INCLUDE_DIRECTORIES directive. It always
takes the value as it is:
Passing
MY_SPECIAL_INCLUDE32=/foo/bar/32bit/include:/foo/bar/include
to INCLUDE_DIRECTORIES like
INCLU
23 matches
Mail list logo
