:
Am 22.04.2013 14:26, schrieb Petr Kmoch:
Hi all.
I'm using CMake 2.8.10.2 to do a Visual Studio 2010 64-bit build, and I
encountered a weird problem with the CMake configure step failing, with
the
following output:
CMake Error at C:/Program Files (x86)/CMake
2.8/share/cmake-2.8/Modules
Hi John,
the primary tool for superbuilds in CMake's arsenal is ExternalProject_Add
from module ExternalProject. I don't have much experience with it, but you
can read its docs to see if it could help you.
Petr
On Thu, Apr 18, 2013 at 5:38 AM, John Gallagher
johnkgallagher+cm...@gmail.com
?
Thanks,
Lloyd
On Fri, Apr 12, 2013 at 4:55 PM, Petr Kmoch petr.km...@gmail.com wrote:
1. Can you post tests/CMakeLists.txt (or at least the parts relevant to
creating test_rev)?
2. Does it work if you use the enhanced signature of add_test? I mean
'add_test(NAME Test COMMAND
issues should be handled by RPATH/RUNPATH.
Petr
On Mon, Apr 15, 2013 at 10:58 AM, Lloyd lloydkl.t...@gmail.com wrote:
On Mon, Apr 15, 2013 at 12:10 PM, Petr Kmoch petr.km...@gmail.com wrote:
The errors VS spews out aren't really useful. However, if you go to
${CMAKE_BINARY_DIR}/Testing
Hi Lloyd.
Do you actually have a target (executable) named test_rev? And have you
built it before running RUN_TESTS? RUN_TEST (or its Makefile equivalent
'make test') doesn't automatically build the test executables before
running them.
Petr
On Fri, Apr 12, 2013 at 1:08 PM, Lloyd
the test and it is in
E:\CMakeDemo\BuildDir\tests\Debug\test_rev.exe
I don't know the right way to locate this test executable for cmake
Thanks,
Lloyd
On Fri, Apr 12, 2013 at 4:42 PM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Lloyd.
Do you actually have a target (executable) named
wrapper
script: call CMake on line 1 and your perl script on line 2...
On Apr 9, 2013, at 8:51 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi.
Just for context: I've filed a request for generic support for
post-generation commands some time ago (
http://public.kitware.com/Bug/view.php?id
Hi Braden,
the purpose of CMAKE_CFG_INTDIR is to expand to something that is
meaningful to the build system you're using. It's a way to transport
information from CMake-time (when your CMakeLists are processed) to
build-time (when you run a build).
The exact value of CMAKE_CFG_INTDIR depends on
Hi all,
I've recently found a nice site for regex trouble: http://regexpal.com/
Maybe you can find it useful.
Petr
On Mon, Mar 18, 2013 at 7:48 PM, Andreas Schneider a...@cryptomilk.org wrote:
On Monday 18 March 2013 18:00:29 David Cole wrote:
Use “^.*” at the beginning of the regex and
Hi all,
I've created a small patch with a few minor documentation
enhancements, mainly things I was looking for in the docs but didn't
find them there. I hope you find it useful.
Petr
0001-Enhnance-documentation.patch
Description: Binary data
--
Powered by www.kitware.com
Visit other Kitware
Hi Julien,
CMake correctly identifies that gen.90f depends on gen.f90.sh, but you
have no code to tell CMake that usegen.f90 depends on gen.f90. The
following should do the trick:
set_property(SOURCE usegen.f90 PROPERTY OBJECT_DEPENDS
${CMAKE_BINARY_DIR}/gen.f90)
Petr
On Mon, Mar 11, 2013 at
Hi Jupiter,
regarding your second question: you'd need to escape the nested
quotes. Also, I'm not sure if 'not exists' can be given in lowercase.
However, I'd strongly suggest using install(SCRIPT ...) instead of
install(CODE ...), precisely because of the escaping issues.
Petr
On Mon, Mar 11,
correct me.
Thank you.
Kind regards.
Jupiter
Petr Kmoch wrote
Hi Jupiter,
regarding your second question: you'd need to escape the nested
quotes. Also, I'm not sure if 'not exists' can be given in lowercase.
However, I'd strongly suggest using install(SCRIPT ...) instead of
install(CODE
Hi Magnus,
I've never worked with Eclipse, but source_group() might be the
command you're looking for.
Petr
On Mon, Mar 11, 2013 at 4:17 PM, Magnus Therning mag...@therning.org wrote:
In the project I work on we have tools that generate quite a few
header files, but they are all generated
Hi Peter.
How is it not working?
Also, I believe you shouldn't call enable_language() before calling
project(). And since you apparently need Fortran unconditionally, you
might simply start your CMakeList like this:
cmake_minimum_required(VERSION 2.8)
project(MYFORTRANLIB C CXX Fortran)
# ...
Hi Luc,
would it help of you changed the command to run 'sh' and have it
execute 'cp lib/*.so /usr/local/lib'? Just a wild idea.
Petr
On Mon, Mar 4, 2013 at 12:50 PM, Luc J. Bourhis luc_j_bour...@mac.com wrote:
Hi,
ExternalProject_Add is a fantastic tool but I have got one issue with it.
Hi Neil.
I can only answer your question 3: there are variables like
CMAKE_Fortran_COMPILER and CMAKE_Fortran_COMPILER_ID which you could
use for this purpose. They're documented as CMAKE_LANG_COMPILER etc.
under Variables for Languages.
Petr
On Mon, Feb 18, 2013 at 1:13 AM, Neil Carlson
Hi Bart.
When you look into the documentation of find_package() (in its
Configure mode), you'll find a list of paths and prefixes the find
machanism uses. You should be able to set some of those prefixes to
where your local installation of OpenCV is.
Petr
On Thu, Feb 14, 2013 at 12:09 PM, Bart
Hi Olaf.
You're missing a DEPENDS argument in your custom command to make
${foo_STATIC_LEXER_HPP} depend on ${foo_LEXER_HPP}. (Or, in your case,
MAIN_DEPENDENCY would probably be more appropriate).
Next, the custom target driving the lexer generation should depend on
its output, not its input -
Hi all.
I have a problem with Fortran_MODULE_DIRECTORY only being applied in the
first of several subdirectory projects. Here's a simplified setup to
demonstrate the issue. It has a toplevel C++ project and two subdirectory
projects which use Fortran:
$cat source_dir/CMakeLists.txt:
I forgot to add that if, immediately after running CMake, I run it again
(without changing a single file), the flags -module foobar appear in the
sub2/.../flags.cmake as well.
Petr
On Tue, Feb 12, 2013 at 2:15 PM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all.
I have a problem
Thanks very much for clearing this up. I fully understand my setup is a
little unorthodox.
I'm glad I can now concentrate on finding a workaround instead of wondering
what I'm doing wrong.
On Tue, Feb 12, 2013 at 3:06 PM, Brad King brad.k...@kitware.com wrote:
On 02/12/2013 08:15 AM, Petr
Hi all.
I believe the reason is that EXCLUDE_FROM_ALL excludes the target from the
default 'all' target (Makefiles), which is represented by the custom target
ALL_BUILD in Visual Studio. EXCLUDE_FROM_DEFAULT_BUILD instead works with
Visual Studio's Build Solution command, which has no direct
Hi Andreas.
Would it be an option to change your VS settings and in 'Tools Options
Projects and Solutions Build and Run', uncheck Only build startup
projects and dependencies on Run? If you do that, it will check/rebuild
everything when you hit F5, not just the startup project and its
Hi Bryn,
you might want to experiment with the (somewhat erratic) global variable
CMAKE_USE_RELATIVE_PATHS.
Petr
On Thu, Jan 31, 2013 at 9:04 PM, Bryn Aspestrand
baspestr...@sugarsync.comwrote:
Yeah, CMAKE changed to relative pathing in VS2010 projects which fixes the
issue with a bug in VS
Hi Witold.
Based on this feature-support matrix:
http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport , it seems gcc 4.6
doesn't support override (even with the C++0x flag). I just verified this
without CMake.
Petr
On Thu, Jan 17, 2013 at 10:30 AM, Witold E Wolski wewol...@gmail.comwrote:
I
Hi Willy.
I believe the property ADDITIONAL_MAKE_CLEAN_FILES should be set on the
directory which *creates* the file, not the one which contains it on disk.
Petr
On Tue, Jan 8, 2013 at 10:42 AM, Willy Lambert lambert.wi...@gmail.comwrote:
Hi all,
When I build my project I use the
Hi all.
On Windows, Visual Studio 2010, some machines in our company experience
this error (
http://connect.microsoft.com/VisualStudio/feedback/details/540902/tracker-exe-response-file-not-found)
when detecting C compiler, which makes it impossible to use CMake on
them. The workaround (mentioned
Hi Martin,
if you only want to install files which match something, you need to add
FILES_MATCHING to the insall() command (before the first pattern/regex),
like this:
install(DIRECTORY start/ DESTINATION images FILES_MATCHING REGEX
.*/\\.Images/.*)
(I've also added backslashes, since you
Hi all,
VS 2012 and VS 2010 installed together *can* actually cause problems (it
certainly did for me). I was getting exactly the same error as David Doria,
and I had to install a service pack for 2010 to overcome it. See e.g.
http://public.kitware.com/Bug/view.php?id=8996
On Wed, Nov 7, 2012 at 8:40 PM, David Cole david.c...@kitware.com wrote:
Hi all,
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here.
Example one-line reply:
Hi Julian.
CMake 2.8.10 introduced target properties PDB_NAME[_CONFIG] and
PDB_OUTPUT_DIRECTORY[_CONFIG] which you can use to control location of
.pdb files. You can also set variable CMAKE_PDB_OUTPUT_DIRECTORY to
pre-initialise the directory settings.
Petr
On Wed, Nov 14, 2012 at 1:57 PM,
http://public.kitware.com/Bug/view.php?id=8996
On Wed, Nov 7, 2012 at 8:40 PM, David Cole david.c...@kitware.com wrote:
Hi all,
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here.
Example one-line reply:
On Tue, Nov 13, 2012 at 4:55 PM, Brad King brad.k...@kitware.com wrote:
On 11/13/2012 09:18 AM, Brad King wrote:
On 11/12/2012 08:25 AM, Petr Kmoch wrote:
Fixed (that is, works for me) and rebased to 3b7abfd.
Thanks. Applied:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h
ALL
DEPENDS ${out}
)
On Wed, Nov 7, 2012 at 2:53 AM, Petr Kmoch petr.km...@gmail.com wrote:
Yes, there is a limitation. You can't use them in OUTPUT. See
http://public.kitware.com/Bug/view.php?id=12877
Petr
On Wed, Nov 7, 2012 at 12:26 AM, Robert Dailey rcdailey.li
no sense to run the tests when using msbuild. Shall I send
you a patch to disable the tests for it? And if so, on what commit should I
base it?
Petr
On Wed, Oct 17, 2012 at 12:53 PM, Brad King brad.k...@kitware.com wrote:
On 10/17/2012 3:24 AM, Petr Kmoch wrote:
I'm a bit confused. We
On Tue, Nov 6, 2012 at 2:31 PM, Brad King brad.k...@kitware.com wrote:
On 11/06/2012 08:22 AM, Petr Kmoch wrote:
I verified that the tests fail when CMAKE_MAKE_PROGRAM points to msbuild,
because 'cmake --build' does not operate on the .sln in such case.
FYI, a recent issue was filed
Yes, there is a limitation. You can't use them in OUTPUT. See
http://public.kitware.com/Bug/view.php?id=12877
Petr
On Wed, Nov 7, 2012 at 12:26 AM, Robert Dailey rcdailey.li...@gmail.comwrote:
I was specifying that in my path for one of the OUTPUT files in
add_custom_command(). Is there any
Hi Kent.
As you say, there is no current build type in Visual Studio; that depends
on what the user selects in the combo box. If you only need this
information at build time, you can use the generator expression
$CONFIGURATION for this purpose. See the documentation of
add_custom_command(); I
On Mon, Oct 22, 2012 at 4:58 PM, David Cole david.c...@kitware.com wrote:
On Mon, Oct 22, 2012 at 3:22 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Andreas,
thanks for your tip. Unfortunately, 'make -k install' doesn't help, as
the
entire install step is a single command (cmake -P
On Tue, Oct 23, 2012 at 1:07 PM, Eric Noulard eric.noul...@gmail.comwrote:
2012/10/23 David Cole david.c...@kitware.com:
On Tue, Oct 23, 2012 at 2:53 AM, Petr Kmoch petr.km...@gmail.com
wrote:
On Mon, Oct 22, 2012 at 4:58 PM, David Cole david.c...@kitware.com
wrote:
On Mon, Oct 22
PM, Andreas Pakulat ap...@gmx.de wrote:
Hi,
On Sat, Oct 20, 2012 at 11:39 AM, Petr Kmoch petr.km...@gmail.com wrote:
when running the install step of a CMake-generated buildsystem (i.e.
'make
install' or building the VS project INSTALL), the run terminates after
the
first failure (e.g
Hi all,
when running the install step of a CMake-generated buildsystem (i.e. 'make
install' or building the VS project INSTALL), the run terminates after the
first failure (e.g. when it cannot find a file which is to be installed).
Is there a way to globally change this behaviour so that the
On Tue, Oct 16, 2012 at 5:26 PM, Brad King brad.k...@kitware.com wrote:
On 10/16/2012 11:04 AM, Brad King wrote:
I tested it locally on VS 6, 7.1, 8, 9, 10, and 11 all with
spaces in the path. I need to investigate the failures on
the dashboard to identify the problem.
Since we're
Hi,
I tried submitting my first patch recently (Issue 0013587) and I have a few
follow-up questions regarding best practices:
1) Looking at the dashboard, I apparently forgot to quote a path somewhere
in the test and it failed on spaces. What is the preferred way for me to
provide a fix for the
Hi Jakub.
I would try adding quotes around the dereference of THIRD_PARTY_LIBS. That
is:
set_properties(... PATH=${THIRD_PARTY_LIBS} ...)
Petr
On Wed, Oct 10, 2012 at 2:13 PM, Jakub Zakrzewski jzakrzew...@e2e.chwrote:
Hi All.
Could someone explain to me, how properly set environment for
Hi all,
I have a question about tests of CMake itself. I'd like to create a new
feature patch and I would definitely want to supply tests with it. Is there
a standard mechanism (perhaps something like the macro check_cmake_test())
to test that a generated buildsystem (specifically, Visual Studio
Hi Witold.
Using RELATIVE does not change where the files are looked for, only how
they are reported. I believe you need this:
file(GLOB Demo_HEADERS RELATIVE ${CMAKE_SOURCE_DIR}/include include/*.h)
Hope this help.
Petr
On Tue, Oct 9, 2012 at 9:34 AM, Witold E Wolski wewol...@gmail.com
Hi Arindam.
AFAIK, there is no such variable (I'd love to be proven wrong). What I
currently do is hard-code the path:
${${projectName}_BINARY_DIR}/${targetName}.dir/...
Petr
On Sat, Oct 6, 2012 at 1:07 PM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
Hi,
I am using cmake to
AM, Petr Kmoch petr.km...@gmail.com wrote:
Anyone? Any suggestions would be appreciated.
Petr
On Mon, Sep 24, 2012 at 5:16 PM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all,
I seem to have a problem when using add_test(... CONFIGURATIONS ...) and
running 'make test' on Linux. It's
Anyone? Any suggestions would be appreciated.
Petr
On Mon, Sep 24, 2012 at 5:16 PM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all,
I seem to have a problem when using add_test(... CONFIGURATIONS ...) and
running 'make test' on Linux. It's skipping the test.
The CMakeLists.txt contains
Hi Andrew.
Just a clarification: do you actually need the source-gathering file
(currently /project_src/code/client/core/CMakeLists.txt) to be a CMakeList?
If all it does is set up some variables, you might be best off renaming it
e.g. FileSetup.cmake and then including it using include(...) in
Hi all,
I seem to have a problem when using add_test(... CONFIGURATIONS ...) and
running 'make test' on Linux. It's skipping the test.
The CMakeLists.txt contains:
#...
enable_testing()
add_test(NAME test1 CONFIGURATIONS db COMMAND ...)
#...
On Windows, I invoke CMake like this:
cmake
Hi,
just a wild guess: .def files for C++ projects have to list the mangled
names, so if you want the export name to be just testfunc, it should be
declared as 'extern C'.
Petr
On Thu, Sep 13, 2012 at 8:17 AM, Ali Hamdi alh...@gmail.com wrote:
Hello everybody,
I am trying to create a DLL by
Hi Robert.
What you're after is pretty standard cmake. You'll need
add_custom_command(
OUTPUT path_to/generated_header.h path_to/generated_source.cpp
COMMAND midl.exe arguments to midl
other options of add_custom_command as necessary
)
# as many times as necessary (probably once per IDL
Sorry, typo. In the case of add_custom_target(), the files would be listed
as DEPENDS.
Petr
On Tue, Sep 11, 2012 at 9:13 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Robert.
What you're after is pretty standard cmake. You'll need
add_custom_command(
OUTPUT path_to/generated_header.h
Hi Nico.
I don't know, but I would assume this (just like a plethora of other
internals) is set up by a project() call. The rule of thumb is to call
project() a soon as you can.
Petr
On Tue, Sep 11, 2012 at 11:26 AM, Nico Schlömer nico.schloe...@gmail.comwrote:
Hi all,
I'm having problems
Hi all.
I'm on Windows, and I need a DLL composed of multiple static
libraries, any of which can define dllexport functions not otherwise
referenced in the DLL. The problem is that the Visual Studio linker
does not provide flags to link an entire static library (i.e. there is
no equivalent to
Hi Krzysztof.
The easiest way is to list the external file among the target's
sources in add_executable/add_library, if possible.
Petr
On Sun, Sep 9, 2012 at 9:20 PM, Krzysztof k...@limes.com.pl wrote:
How to make a project dependent on an external file? The file could be a
library built by
Hi Eric.
Many thanks for your reply.
On Mon, Sep 10, 2012 at 9:49 AM, Eric Noulard eric.noul...@gmail.com wrote:
2012/9/10 Petr Kmoch petr.km...@gmail.com:
Hi all.
I'm on Windows, and I need a DLL composed of multiple static
libraries, any of which can define dllexport functions
Hi all,
I am using cmake on Windows to generate a vfproj for a Fortran DLL.
This DLL links some object files written in C, using
add_library(OBJECT). For some reason, the library is always considered
out of date, i.e. with every Build solution command (or just Build
on its project), it relinks.
)
add_executable(TestF90_EXE main.f90)
Thanks,
Alexander
2012/9/3 Petr Kmoch petr.km...@gmail.com
Hi Alexander.
CMAKE_EXE_LINKER_FLAGS and similar variables can only be modified
after a call to PROJECT() (the PROJECT() calls sets them up to some
defaults). See if this fixes your issue.
Petr
Hi all.
By default, admin privileges are necessary to run mklink (even for
creating symlinks). However, this can be changed by granting the
SeCreateSymbolicLinkPrivilege privilege (see e.g.
Hi Alexander.
CMAKE_EXE_LINKER_FLAGS and similar variables can only be modified
after a call to PROJECT() (the PROJECT() calls sets them up to some
defaults). See if this fixes your issue.
Petr
On Fri, Aug 31, 2012 at 8:47 PM, Alexander Ivanov
alexander.nik.iva...@gmail.com wrote:
Hello all!
Hi Fabio.
With ALL_BUILD, you're out of luck, but other default cmake targets go
to a group if you set the global property PREDEFINED_TARGETS_FOLDER.
I am afraid I can't help with the other points.
Petr
On Tue, Jul 31, 2012 at 12:02 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
Hi,
I
:-( I'd prefer one of my projects to be
the default, for instance.
Petr
On Tue, Jul 31, 2012 at 3:35 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
On 7/31/12 12:50 PM, Petr Kmoch wrote:
Hi Fabio.
With ALL_BUILD, you're out of luck, but other default cmake targets go
to a group if you set
Hi.
I think you're looking for
...
COMMENT ${line0}\n${line1}\n${line2}\n${line1}\n${line0}
...
Petr
On Mon, Jul 30, 2012 at 11:42 AM, luxInteg lux-in...@btconnect.com wrote:
Greetings
I am learniong cmake. From the documentation:-
add_custom_target(Name [ALL] [command1 [args1...]]
Hi Eli.
You have a typo in the macro: set_target_properties(${testmame} ...
If it's a direct copypaste from your code, it might be the source if the issue.
Petr
On Wed, Jul 11, 2012 at 1:22 AM, Ateljevich, Eli e...@water.ca.gov wrote:
My expectation from the documentation was that runtime
Hi Mateusz,
I am not aware of direct cmake support for preprocessing a file, so I
will only comment on the add_custom_*() part.
You have to create a custom command (using the OUTPUT signature) to
actually do the preprocessing. If you're targetting gcc and Visual
Studio, the command could look
Hi all.
Actually, the MS compilers distinguish and just fine (at least
in my VS 2005 and VS 2010 installation). Dominik, do you perhaps
specify the path to your Math.h in include_directories()?
Petr
On Mon, Jul 9, 2012 at 3:20 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am 09.07.2012 15:07,
Hi Jerome,
you can use two install() commands. I use this often, and I see
nothing wrong with it. As you said, if you want to avoid code
duplication, you can make a macro for it.
Petr
On Wed, Jul 4, 2012 at 9:41 AM, Jérôme Reybert jreyb...@gmail.com wrote:
Hi,
I need to install the same
Hi,
are you setting the global property DEBUG_CONFIGURATIONS anywhere? If
not, cmake does not know which configurations are supposed to be
debug, so it treats all of them as optimized. Try adding the following
after the two set(CMAKE_CONFIGURATION_TYPES ...) commands:
set_property(GLOBAL
Hi Brett,
as far as I know, compilation flags come from
CMAKE_lang_FLAGS_config, while linker flags come from
CMAKE_{SHARED|EXE}_LINKER_FLAGS[_config]. So you should be able to
override CMAKE_SHARED_LINKER_FLAGS_Debug (not sure with correct case
for configuration name) and remove -g from there.
Hi all.
file(REMOVE ...) does not seem to be able to remove a file which is a
symbolic link (neither on NFS nor on NTFS). Is there a
platform-independent way to remove a symlink from within cmake, or do
I have to resort to if() and execute_process()?
Thanks for any replies.
Petr
--
Powered by
Hi Benjamin.
What you're dealing with is the runtime not finding the DLL, and cmake
has little control over that. One solution would be to set both
library and the executable to build in the same directory (using
set_property(TARGET trgt PROPERTY RUNTIME_OUTPUT_DIRECTORY whatever).
Two other
Hi Michele,
I don't know how it is in this particular case, but some
configuration-specific variable, property etc. names are
case-sensitive. I believe the default configuraions are called Debug
and Release. You could try setting
IMPORTED_LINK_INTERFACE_LIBRARIES_Debug.
Petr
On Fri, Jun 22,
Hi Leif.
I'm not on a machine with cmake now so I can't test, but I guess the
variable PROJECT_NAME is empty if no project() has been called yet.
Petr
On Fri, Jun 22, 2012 at 6:10 PM, Leif Walsh leif.wa...@gmail.com wrote:
Suppose I have two projects, A and B. A builds a shared lib that links
Hi Joseph.
The following should work:
FOREACH(dir dir1 dir2)
SOURCE_GROUP(${dir}\\inc REGULAR_EXPRESSION ${dir}/.*\\.h)
SOURCE_GROUP(${dir}\\src REGULAR_EXPRESSION ${dir}/.*\\.cpp)
SOURCE_GROUP(${dir}\\inl REGULAR_EXPRESSION ${dir}/.*\\.inl)
ENDFOREACH()
Petr
On Tue, Jun 19, 2012 at 5:05
Hi all,
is it possible to somehow set the command which 'make clean' or
'Build-Clean in VS' performs for a file? My situation is that a
custom command creates a symlink to a directory. I'd like to delete
this symlink when 'Clean' is performed. This fails silently on Unix
(no action is performed)
Hi Daniel.
Yes, that's how Visual Studio shows excluded files. If you exclude a
file by setting its Excluded from build property manually, you get
the same.
Petr
On Tue, Jun 12, 2012 at 8:31 PM, Daniel Dekkers d.dekk...@cthrough.nl wrote:
Ok, great, works.
So I guess the little red stop-sign
executables in a single solution and they
all get their own additional CopyResources target.
But, ok...
Thanks!
Daniel
-Oorspronkelijk bericht-
Van: Tim Hutton [mailto:tim.hut...@gmail.com]
Verzonden: woensdag 13 juni 2012 12:42
Aan: Daniel Dekkers
CC: Petr Kmoch; cmake@cmake.org
Hi Mikael.
I don't think such functionality is built in, but it seems doable with
cmake functions and custom commands/targets.
Do you want the copying to happen at configure time (running cmake) or
build time (running make or similar)? For the former, you can use
`configure_file(... COPYONLY
Hi Jonathan.
On Tue, May 29, 2012 at 8:41 PM, Jonathan Romero jonn...@jonnyro.com wrote:
Hello,
I am running a build using cmake using the Meego 1.2 toolchain (long
story). This particular toolchain requires the --sysroot option to be used
to find any libraries it requires.
set
Hi Johannes,
the only solution I can think of is something like:
#
option(WITH_A ...)
option(WITH_B ...)
set(MySources always/present/files ...)
if(WITH_A)
list(APPEND MySources files/for/a ...)
endif()
if(WITH_B)
list(APPEND MySources files/for/b ...)
endif()
add_executable(MyExec
2012/5/22 Petr Kmoch petr.km...@gmail.com
Hi,
try as I might, I can't see a difference between the output and
expected output. Perhaps a copy-paste error?
Petr
On Tue, May 22, 2012 at 3:07 AM, Marmot Ken realwan...@gmail.com wrote:
here is the function :
FUNCTION
Hi,
try as I might, I can't see a difference between the output and
expected output. Perhaps a copy-paste error?
Petr
On Tue, May 22, 2012 at 3:07 AM, Marmot Ken realwan...@gmail.com wrote:
here is the function :
FUNCTION( Append_headers_to_src_list src_list_out src_list_in
Thanks very much for the feedback. I will look into the module stuff,
where the compiler puts it etc.
Petr
On Wed, May 16, 2012 at 10:24 PM, Brad King brad.k...@kitware.com wrote:
On 05/10/2012 03:25 AM, Petr Kmoch wrote:
we're using cmake to generate Intel Fortran .vfproj files and some
Hi David,
there's a target property LINK_INTERFACE_LIBRARIES (and
per-configuration variants) which can be used for this purpose.
Starting with 2.8.7, target_link_libraries() also accepts
LINK_INTERFACE_LIBRARIES as a new argument mode, setting the property
instead of linking.
Petr
On Wed, May
Hi Daniel.
In general, that is not possible with cmake at the moment. What I
currently do is have two custom targets, one for copying to debug, one
for copying to release. It's annoying that both get run in either
configuration, but I couldn't find a better way around it.
There are some
Hi Anton,
you should look into target property LINK_INTERFACE_LIBRARIES (and its
per-configuration variants) which controls transitive linking.
target_link_libraries() also accepts LINK_INTERFACE_LIBRARIES as an
argument mode, which sets the property instead of linking.
Petr
On Thu, May 17,
Anyone? Surely there must be a reason for adding those directories.
Petr
On Thu, May 10, 2012 at 9:25 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all,
we're using cmake to generate Intel Fortran .vfproj files and some of
my developers were asking why include directories in the project
Hi Gonzalo,
the problem is cmake didn't find qmake. The safest way to use cmake
with Qt on Windows is to run cmake from a Qt-aware command line (or
have qmake in your PATH). There should be a shortcut to a Qt command
prompt installed in your Start menu. If it's not, you can create your
own:
Hi Cristian.
There are two ways to go about this, either using OUTPUT_NAME or
PROJECT_LABEL. It also depends on what you want the target name in
Makefiles to be:
(1)
add_executable(def) #name of Makefile target and executable will be `def'
set_property(TARGET def PROPERTY PROJECT_LABEL ABC)
Hi all,
we're using cmake to generate Intel Fortran .vfproj files and some of
my developers were asking why include directories in the project
always include X and X/config_name for every directory X specified
via include_directories(). Looking at cmake source code, the lines
responsible seem to
The closest I've come to solving this problem is that for each test
${testTarget}, I add two cmake tests:
add_test(NAME build_${testTarget} COMMAND ${CMAKE_COMMAND} --build
${CMAKE_BINARY_DIR} --target ${testTarget} --config
$CONFIGURATION)
add_test(NAME someName COMMAND ${testTarget} ...)
It
...@gmail.com wrote:
So you run 'ctest -R testTarget' and it picks up the build test too?
Hmm. Thanks.
On Wed, 9 May 2012, Petr Kmoch wrote:
The closest I've come to solving this problem is that for each test
${testTarget}, I add two cmake tests:
add_test(NAME build_${testTarget} COMMAND
Hi.
Custom commands are executed at build time (that is, when you do a
build in Visual Studio), not at generation time (when cmake is
running). There is no way to hook something to the end of the
generation process itself (see
http://public.kitware.com/Bug/view.php?id=13020 ).
BTW, it's
the solution.
For this I need all my vcxproj files at a specific place.
But now I have to look for another way
Antje
-Ursprüngliche Nachricht-
Von: Petr Kmoch [mailto:petr.km...@gmail.com]
Gesendet: Mittwoch, 9. Mai 2012 16:46
An: Antje Kühn
Cc: cmake@cmake.org
Betreff: Re: [CMake
In that case, cmake should already be generating this for you, from
your toplevel CMakeLists.txt file.
On Wed, May 9, 2012 at 5:23 PM, Antje Kühn antje.ku...@online.de wrote:
No, I need one main solution that bundles all the other subprojects.
-Ursprüngliche Nachricht-
Von: Petr Kmoch
Unfortunately, this only works for single-configuration generators
(Makefiles). If you're targetting Visual Studio as well, you're pretty
much out of luck. I see this as one of the major issues with cmake.
A possible workaround is to move the target(s) in question to a
separate CMakeLists.txt
201 - 300 of 312 matches
Mail list logo
