On 03/05/2012 05:59 PM, Andrea Crotti wrote:
> I'm having the following behaviour, and I can't quite understand the
> error message:
>
> ..
> Built target psi.utility_install
> ..
> make[3]: *** No rule to make target `psi.utility_install', needed by
> `CMakeFiles/install_all_eggs'. Stop.
> mak
On 03/05/2012 10:43 AM, Johannes Zarl wrote:
> On Saturday 03 March 2012, 02:29:05, Robert Dailey wrote:
>> Well you're really comparing apples to oranges. C++ nested scoping rules
>> really have nothing to do with two separate functions sharing scoped
>> variables. It doesn't even really serve as
2012/3/6 Ajay Panyala :
> Hello,
>
> Is there anyway that cmake could figure out the shell (bash,csh,..)
> that is being use when cmake is invoked on the command line ?
May be you can check $ENV{SHELL} ?
Why would you like to do that?
Usually when using CMake one tries to avoid shell/command inte
On 03/04/2012 11:01 AM, Andreas Guther wrote:
> Hello,
>
> thanks for the responses. The problem I have is, that we have more than one
> application in the directory. So if I put an CMakeLists.txt in the Src
> directory I do not have the choice (only by options). I would prefer a
> solution whe
Hello,
Is there anyway that cmake could figure out the shell (bash,csh,..)
that is being use when cmake is invoked on the command line ?
Thanks
Ajay
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
Hello All,
I am trying to attach a custom POST_BUILD command to the ALL_BUILD target.
I've tried adding the following at the bottom of my root CMakeLists.txt
file but the Post Event never shows up in Visual Studio. I have been able
to get it to work for sub projects, just not ALL_BUILD. Has anyone
I have test and package configurations on my project, I want:
cmake .
make package
to run force injection of the "test" target prior to building the
package target.
Can it be done? How? :)
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitwar
On Sun, 4 Mar 2012 22:15:52 +0100
Andreas Pakulat wrote:
>No, for those three at least you also don't need link_directories. The
>find-modules for all 3 provide the absolute paths to the libraries in
>CMake variables which you can use with target_link_libraries directly
>and it'll just work.
Th
On 05.03.12 14:14:13, Robert Dailey wrote:
> The docs aren't updated to reflect this so I just wanted to make sure. I
> didn't have time to run through the source code (you Linux people and your
> fancy 'git grep' commands :P )
You know git including git grep also works on windows (and no I'm not
2012/3/5 Robert Dailey :
> The docs aren't updated to reflect this so I just wanted to make sure.
Patch for documentation may be accepted as well :-]
> I didn't have time to run through the source code (you Linux people and your
> fancy 'git grep' commands :P )
You Windows people and your need t
The docs aren't updated to reflect this so I just wanted to make sure. I
didn't have time to run through the source code (you Linux people and your
fancy 'git grep' commands :P )
-
Robert Dailey
On Mon, Mar 5, 2012 at 11:58 AM, David Cole wrote:
> Correct. Partial output from 'git grep
> if(${GrammarSource}/test.g IS_NEWER_THAN ${PROJECT_BINARY_DIR}/test.g)
> ADD_CUSTOM_TARGET(...)
> ADD_CUSTOM_COMMAND(...)
>
> i.e I am totally avoiding the process of rebuilding the test.g file and
> copying the generated files to build/parser
> *IF* test.g has not been modified.
...and
Correct. Partial output from 'git grep MSVC_VERSION' in the CMake source tree:
$ git grep MSVC_VERSION
...
Modules/CMakeVS10FindMake.cmake:SET(MSVC_VERSION 1600)
Modules/CMakeVS11FindMake.cmake:SET(MSVC_VERSION 1700)
Modules/CMakeVS6FindMake.cmake:SET(MSVC_VERSION 1200)
Modules/CMakeVS71FindMake.c
I'm assuming MSVC_VERSION will be 1700 for MSVC11. Is this correct?
-
Robert Dailey
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.or
I'm having the following behaviour, and I can't quite understand the
error message:
..
Built target psi.utility_install
..
make[3]: *** No rule to make target `psi.utility_install', needed by
`CMakeFiles/install_all_eggs'. Stop.
make[2]: *** [CMakeFiles/install_all_eggs.dir/all] Error 2
make[
On Mon, Mar 5, 2012 at 3:40 AM, Quân Phạm Minh wrote:
> how do in cmake to get visual studio 2008 project file have structure with
> some folders below:
>
> project
> + Form Files
> + Generate Files
> + Resource Files
> + Header Files
> + Source Files
With the
This is for menu items in the Windows Start menu. Is that what you mean?
See the file CMakeCPackOptions.cmake.in in CMake's own source tree
that has code in it like this:
if(CPACK_GENERATOR MATCHES "NSIS")
...
SET(CPACK_NSIS_MENU_LINKS
# ... pairs of (filenames or urls, text for menu ite
Hello,
I am trying to cross-compile a project containing C, C++ and Fortran
source files with mingw64 on a Debian host (Linux) with CMake 2.8.7:
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
project ( FOO CXX C Fortran )
include ( FortranCInterface )
FortranCInterface_HEADER (
Hello,
for whatever it is worth, C-style preprocessor commands
are a non-standard feature. The Fortran standard itself
defines only the "INCLUDE" statement (or directive).
Perhaps you can solve this in a standard way by moving the
logic to the CMakeLists.txt files rather than relying
on (possibly
On Saturday 03 March 2012, 02:29:05, Robert Dailey wrote:
> Well you're really comparing apples to oranges. C++ nested scoping rules
> really have nothing to do with two separate functions sharing scoped
> variables. It doesn't even really serve as a good analogy, so I can't be
> 100% certain what
how do in cmake to get visual studio 2008 project file have structure with
some folders below:
project
+ Form Files
+ Generate Files
+ Resource Files
+ Header Files
+ Source Files
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:/
21 matches
Mail list logo
