2012/6/21 Bill Lorensen :
> If an INSTALL command does not provide a COMPONENT, it seems that a
> component named "Unspecified" is created.
This is true.
> This is not mentioned
> anywhere in the cmake documentation as far as I can tell.
This is almost true, Alex has implemented a way to control
2012/6/21 Bill Lorensen :
> According to the documentation, an install command like this:
> INSTALL (
> TARGETS myTarget
> EXPORT myExportedTargets
> RUNTIME DESTINATION bin COMPONENT component1
> LIBRARY DESTINATION lib COMPONENT component2
> ARCHIVE DESTINATION bin COMPONENT compon
2012/6/21 Ateljevich, Eli :
> Eric
> I have improved my envvar usage a bit further, I hope, by saying
> include_directories( $ENV{NETCDF_INC} )
> rather than
> include_directories( ${NETCDF_INC} )
This is not the way CMake is supposed to work.
Normally you use
find_library, file_path, etc... in o
Has no one an idea on how to do so or is such functionality missing?Thanks in advanceBest RegardsAm 15. Jun 2012 um 08:38 schrieb NoRulez :Hello David,but the problem is, that the timestamp is one day behind, so this doesn't work and I get previous revisions. (Our nightly build starts at 23:00 and
If an INSTALL command does not provide a COMPONENT, it seems that a
component named "Unspecified" is created. This is not mentioned
anywhere in the cmake documentation as far as I can tell.
This cmake file illustrates the problem:
cmake_minimum_required(VERSION 2.8)
project(bug)
add_executable(m
According to the documentation, an install command like this:
INSTALL (
TARGETS myTarget
EXPORT myExportedTargets
RUNTIME DESTINATION bin COMPONENT component1
LIBRARY DESTINATION lib COMPONENT component2
ARCHIVE DESTINATION bin COMPONENT component3
)
should produce 3 componen
Put the "include(CTest)" line in your top level CMakeLists.txt file.
Do a full clean re-configure (remove the "build" directory, make a new
empty "build" directory and run CMake again).
If it still happens after that, we need more details about your project.
You should be able to build "Experime
Well, thanks to your hints, I did end up resolving this by finding a user error
in the environment that would not have affected make.
So ... worst user post I have ever made, but you did teach me a lot at the
beginning about the environment that would have killed me soon enough.
E
-Origin
Eric
I have improved my envvar usage a bit further, I hope, by saying
include_directories( $ENV{NETCDF_INC} )
rather than
include_directories( ${NETCDF_INC} )
However, I am now quite sure that what is happening is when I put hardwired
absolute paths in include_directories it is used as-is, but
Hi Alexander,
They are there - hidden :)
Thank you.
Jana
--
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.org/Wiki/CMake_FAQ
Follow this link
Hi,
More generally speaking, I'm looking a way to query the existing
configuration in terms of
- what are the libraries, executables, tests, etc...
- properties, compiler flags
declared through out various CMakeLists.txt
and WHERE they are declared ie in which directory (package)
This is also
On Wednesday 20 June 2012, Jana Sefcikova wrote:
> Dear users,
> I am new in CMake and I followed tutorial
> http://www.vtk.org/Wiki/Eclipse_CDT4_Generator , downloaded latest c++
> Eclipse , my cmake version is 2.8.7
>
> I obtained following warning/error ? during cmake configuration of my
> proj
Asking around here at NVIDIA, it looks like you can replace the linker in
VS 2010 (MSBuild probably has the ability), but VS 2008 doesn't support
this.
On Wed, Jun 20, 2012 at 12:53 PM, David Cole wrote:
> The VS generator does not use that variable, and I don't know the exact
> answer to how th
${CMAKE_CURRENT_BINARY_DIR} returns a directory that contains generated
files, such as vcproj files when generating for visual studio. However,
actual compiled binaries are placed:
${CMAKE_CURRENT_BINARY_DIR}/${target_name}.dir/Debug (for debug
configuration)
Is there a variable or target propert
The VS generator does not use that variable, and I don't know the exact
answer to how this is computed everywhere...
But I strongly suspect that VS simply uses "link.exe" and uses the first
one found within whatever environment is set up in Visual Studio.
To see the environment that is available
But do especially note:
"The path may contain a build-system-specific portion that is replaced at
build time with the configuration getting built (such as
"$(ConfigurationName)" in VS)."
On Wed, Jun 20, 2012 at 2:48 PM, David Cole wrote:
> Yes, with:
>
> http://cmake.org/cmake/help/v2.8.8/c
Yes, with:
http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_tgt:LOCATION
or
http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_tgt:LOCATION_CONFIGfor
per-config values
and:
http://cmake.org/cmake/help/v2.8.8/cmake.html#command:get_filename_component
HTH,
David
On Wed, Jun 20, 2012
Is it possible to change what executable is used for linking in VS targets?
I see CMAKE_LINKER, but the variable says "CMAKE_LINKER-NOTFOUND", which
leads me to believe that the VS generator doesn't use this variable.
Thanks,
James
--
Powered by www.kitware.com
Visit other Kitware open-source p
If I were to try to do this *after* calling add_executable() or
add_library(), would it be easier to obtain?
On Wed, Jun 20, 2012 at 12:54 PM, Thompson, K T wrote:
> Robert,
>
> ** **
>
> I’m not sure this is exactly what you are looking for, but you may be able
> to use “generator expressi
Yes, it was implemented as part of supporting another feature, and was left
undocumented at the time.
And it stuck.
This comment is in the source code, though, and the current implementation
will return "1" or "0" in ${variable}:
/*
FILE(DIFFERENT FILES )
*/
HTH,
David
On Tue, Jun
I appreciate your patience as I seem to be struggling reporting some of the
details properly. The real invocation is and has always been this:
cmake -DCMAKE_Fortran_COMPILER=mpif90 ../src
The CMakeLists.txt is below verbatim.
1. If I change to curly braces I get no -I in the compile command at al
Robert,
I'm not sure this is exactly what you are looking for, but you may be able to
use "generator expressions." See the documentation for add_custom_command for
more details, but basically you can use the expression $ to
retrieve the executable name generated by target 'foo'. I think this
Another note: This has to work the same for both release and debug, and for
both visual studio and makefile generators.
On Wed, Jun 20, 2012 at 12:40 PM, Robert Dailey wrote:
> I'm looking for the quickest and most natural way to get the final binary
> name of a target, ideally before add_executa
I'm looking for the quickest and most natural way to get the final binary
name of a target, ideally before add_executable() or add_library() is
called (not sure if this is possible).
For example, if my executable target's output is fubar.exe, I want to get
"fubar.exe" in a variable.
Any examples?
On Wed, Jun 20, 2012 at 12:04 PM, Eric Noulard wrote:
> 2012/6/20 Robert Dailey :
> > Is there a way to configure separately from generate on the command line?
> > cmake-gui allows this but I do not see an option for this for cmake.exe
>
> I don't think it's possible.
> This command line does what
I received the adive:
include(CTest)
instead of:
enable_testing()
Including CTest.cmake will automatically enable_testing(), but it also
configures the "test configuration file" it's complaining about...
and was rewarded with a working VS 9 project. The test_subtract project
built - as it did b
2012/6/20 Robert Dailey :
> Is there a way to configure separately from generate on the command line?
> cmake-gui allows this but I do not see an option for this for cmake.exe
I don't think it's possible.
This command line does what you want (on Linux):
echo "c q" | ccmake ..
May I ask why do yo
2012/6/20 Ateljevich, Eli :
> Addendum: I should add that by now I have taken the failure line, put a space
> in between the two -I components and run it directly in the shell and
> verified it compiles fine (and without the space it fails as in cmake).
Yes right. Collating -I shall fail, no pro
Is there a way to configure separately from generate on the command line?
cmake-gui allows this but I do not see an option for this for cmake.exe
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-t
Addendum: I should add that by now I have taken the failure line, put a space
in between the two -I components and run it directly in the shell and verified
it compiles fine (and without the space it fails as in cmake).
Hi Eric,
Very kind of you to reply. It is true that my example had some det
2012/6/20 Ateljevich, Eli :
> Hi Eric,
> Very kind of you to reply. It is true that my example had some detritus from
> one of the examples that I did not prune. I apologize for the sloppiness and
> your advice certainly saves me some problems with the linker later. However,
> it does not change
Hi Eric,
Very kind of you to reply. It is true that my example had some detritus from
one of the examples that I did not prune. I apologize for the sloppiness and
your advice certainly saves me some problems with the linker later. However, it
does not change the compile behavior. If I understood
I've encountered a problem with OSX framework detection, I think exposed due to
updating to Xcode 4.3.3 (was previously using 4.3.2), though I'm sure the real
issue is actually in my cmake-files.
It appears that /Library/Frameworks is no longer searched by default (this
makes sense for better S
On 06/19/2012 04:27 PM, Daniel Dekkers wrote:
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
> PROJECT(HeaderOnlyTest)
> SET(SOURCE_FILE main.c)
> SET(RESOURCE_FILE test.xml)
> SET_SOURCE_FILES_PROPERTIES(${RESOURCE_FILE} PROPERTIES HEADER_FILE_ONLY
> TRUE)
> ADD_EXECUTABLE(HeaderOnlyTest ${SOURCE_FILE} ${
cmake_install_example.tar.gz
Description: cmake install example
Hi,
My purpose is to create a package that contains tests validating that
it works well out of the box.
I looked into the mailing list, the documentation, the web in general
and I did not find any relevant way of doing this.
Test
Hi,
I am using install command to package configuration files from source to
destination, but I don't want to overwrite the configuration files if the
files exist in destination. Are there any arguments in install(FILES ...)
command to specify NO REPLACE, NO OVERWRITE options to destination
instal
36 matches
Mail list logo
