Thanks, I understand it now.
Vikas
From: David Cole [mailto:david.c...@kitware.com]
Sent: 19 February 2010 18:12
To: Chauhan, Vikas
Cc: Tyler Roscoe; cmake@cmake.org; Bill Hoffman
Subject: Re: [CMake] nmake build with different options at command line
19 February 2010 16:09
> To: Chauhan, Vikas
> Cc: cmake@cmake.org; Bill Hoffman
> Subject: Re: [CMake] nmake build with different options at command
line
>
> On Fri, Feb 19, 2010 at 08:03:59AM -0800, Tyler Roscoe wrote:
> > On Fri, Feb 19, 2010 at 11:19:18AM -, Chauhan, Vika
Thanks but what is the option when we use nmake to build?
-Vikas
> -Original Message-
> From: Tyler Roscoe [mailto:ty...@cryptio.net]
> Sent: 18 February 2010 17:09
> To: Chauhan, Vikas
> Cc: Bill Hoffman; cmake@cmake.org
> Subject: Re: [CMake] nmake build with di
0 13:09
> To: Chauhan, Vikas
> Cc: cmake@cmake.org
> Subject: Re: [CMake] nmake build with different options at command
line
>
> Chauhan, Vikas wrote:
> > Hi,
> >
> > Is it possible to specify the build options such as release/debug
etc
> > when buildin
Hi,
Is it possible to specify the build options such as release/debug etc
when building the nmake files generated by cmake ?
Thanks,
Vikas
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/ope
Thanks but how do I integrate vcbuild or msbuild with cmake ?
Vikas
> -Original Message-
> From: John Drescher [mailto:dresche...@gmail.com]
> Sent: 24 January 2010 21:52
> To: Chauhan, Vikas
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Specifying multiple build
Hi,
Can you please help as how I could specify the number of threads to be
used in the command line builds i.e. something like
(For nmake)
Cmd > nmake -j5
(For Visual Studio 2008)
cmd> cmake --build . -j5
Thanks,
Vikas
___
Powered by www.kitware.com
V
Hi,
I have a very interesting problem. It is described below.
I have two projects Proj1 & Proj2 under a top level root directory.
Now, the build steps are as follows:
1. Build Proj1 into Proj1.exe
2. Execute Proj1.exe and it generates source1.cpp as an output (it
is a source file gener
Mike, Eric & John - thanks very much for the help.
I will work on these ideas.
Regards,
Vikas
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf
> Of John Drescher
> Sent: 20 January 2010 18:53
> To: Eric Noulard
> Cc: cmake@cmake.org
> Subjec
Thanks for the quick reply Mike.
Regards,
Vikas
> -Original Message-
> From: Mike Jackson [mailto:mike.jack...@bluequartz.net]
> Sent: 20 January 2010 17:21
> To: Chauhan, Vikas
> Cc: cmake@cmake.org
> Subject: Re: [CMake] How to customise filters in cmake generated
pro
Hi,
At present I have written my source code for VS2008. I use cmake to
generate VS2008 project files.
If I wanted to switch the compiler to gcc then is it possible to use the
same cmakelists.txt that I have in my source tree & generate the nmake
files or makefiles or vcproj files to use gcc compi
Hi,
Would you have any ideas on how I could organise the filters that are
present in the Cmake generated vcproj files. At present it just
generates filters "Source Files" & "Header Files" .
If I want to include header files from different functional areas then I
how can I create new filters, for
>
> Remove this CMakeCache.txt file, and re-run and it should work.
>
> I would start with a clean build tree and source tree. If you have
> ever run cmake in-source, clean your source tree so that it has no
> generated stuff in it. Also, remove the entire build tree, then you
> should be fin
> Can you try this:
>
>
> 1. Create a new directory:
> mkdir foo
> 2. Create a CMakeLists.txt file in foo
> project(foo)
> add_library(foo bar.c)
>
> Create an empty file bar.c.
>
> 3. Create a build directory under foo:
> mkdir build
>
> 4. run cmake
>
> cd build
> cmake -G"NMake Makefiles"
From: David Cole [mailto:david.c...@kitware.com]
Sent: 14 January 2010 17:58
To: Chauhan, Vikas
Cc: Bill Hoffman; cmake@cmake.org
Subject: Re: [CMake] using cmake on windows - query on existing targets
Get rid of the quotes in this part of your PATH:
"C:\Prog
> -Original Message-
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
> Sent: 14 January 2010 16:19
> To: Chauhan, Vikas
> Cc: Bill Hoffman; cmake@cmake.org
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
> Chauhan, Vikas wrote
> -Original Message-
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
> Sent: 14 January 2010 13:57
> To: Chauhan, Vikas
> Cc: Bill Hoffman; cmake@cmake.org
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
&
From: c...@lambda.nu [mailto:c...@lambda.nu] On Behalf Of Chris Hillery
Sent: 13 January 2010 03:00
To: Bill Hoffman
Cc: Chauhan, Vikas; cmake@cmake.org
Subject: Re: [CMake] using cmake on windows - query on existing targets
On Tue, Jan 12, 2010 at 2:04
> -Original Message-
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
> Sent: 12 January 2010 22:05
> To: Chauhan, Vikas
> Cc: Eric Noulard; cmake@cmake.org
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
>
> >
>
> > Did you try the Nmake generator and call
> >
> > nmake help
> >
> Thanks, I tried using nmake generator i.e. - cmake ../ -G "NMake
Makefiles"- but
> it does not work in cmake 2.8. It fails to find the compiler. However
the
> command - cmake ../ -G "Visual Studio 9 2008" - works fine. The err
> > I understand what you mean and it is similar to what the macro suggested
> > by Alex does.
> > However, I do not want a developer to have a need to change setting in
> > the cmake GUI for what I need.
> >
> > What I want is that:
> > 1. the user should be able to see a list of components & sub
> > Actually, when I used the macro I found that though this macro gives
> > a
> > useful functionality it is not exactly what I wanted.
> >
> > What I want to do can be illustrated the following example:
> > I have a main project/dir - projectSystem
> > I have three component/dir - projectcomponen
> -Original Message-
> From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
> Sent: 06 January 2010 21:24
> To: cmake@cmake.org
> Cc: Chauhan, Vikas
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
> On Wednesday 06 January 20
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf
> Of Andreas Pakulat
> Sent: 10 January 2010 21:39
> To: cmake@cmake.org
> Subject: Re: [CMake] FindBoost.cmake to find the boost libraries
>
> On 10.01.10 19:55:
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf
> Of Andreas Pakulat
> Sent: 10 January 2010 17:51
> To: cmake@cmake.org
> Subject: Re: [CMake] FindBoost.cmake to find the boost libraries
>
> On 10.01.10 15:57:
Hi all,
I am using the code below in cmakelists.txt to find the boost libraries
using cmake 2.8.
After the execution "Boost_LIBRARIES" does not contain anything. Am I
correct in assuming that this variable must be populated with the list
of boost libraries?
Also, I am not sure how do I get the ap
Hi,
I guess there is no end to wishes & this is another example of it.
Is it possible to get a coloured output on windows using a build command
like: cmake --build . ?
Currently is it because dos cmd window doesn't support it or there is
some other reason?
Thanks,
Vikas
> -Original Message-
> From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
> Sent: 06 January 2010 21:24
> To: cmake@cmake.org
> Cc: Chauhan, Vikas
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
> On Wednesday 06 January 20
> -Original Message-
> From: John Drescher [mailto:dresche...@gmail.com]
> Sent: 06 January 2010 19:57
> To: Chauhan, Vikas; CMake mailing list
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
>
> I am going to only answer 1 part of this.
Hi,
I am quite new to using cmake and at the moment I am trying to find my
way through it.
I was wondering how we can query different targets on windows when using
cmake.
For example: I may have a set of separate directories(each containing a
project) and from the top level root directory, I wa
30 matches
Mail list logo
