I'm playing with some of the new cmake 2.8.11 features and an example I saw had
this:
set_property(TARGET foo PROPERTY
INTERFACE_INCLUDE_DIRECTORIES
"$"
"$"
)
I can see it put the expanded version of "${CMAKE_INSTALL_PREFIX}/include" in
my export file, but I want i
Sounds pretty good!
One question remains:
Suppose I have components A, B, C, where both A and B depend on C.
The link line that I'd pull in with
FIND_PACKAGE(Mypackage COMPONENTS A B)
Would be
, , ,
where all of those could be sets. Is there a way to avoid including
C's libs twice? (Is that des
I'm having a problem with something pretty basic, so I'm wondering what I'm
doing wrong.
In my build process, I want to use PyInstaller to generate an EXE. Due to
the way the source code is laid out, the scripts for this PyInstaller setup
are split among several directories. In addition, I need so
> Perhaps it would help if I explained these 2 different ways of using CTest.
/me slaps forehead...
Indeed, this clarifies quite a few things. I hadn't considered
those two ways as distinct, but merely complementing each other,
and wondered about the apparently conflicting documentation.
I will
On Tuesday, April 09, 2013 04:42:57 PM Martin Baute wrote:
> Am 09.04.2013 16:29, schrieb Clinton Stimpson:
> > How are the config settings and binary path for CTest already given
> > in the
> > CMakeLists.txt file? Normally, a CMakeLists.txt file does not have a
> > hardcoded binary path, nor doe
Hello,
I am working on a project called Alpha, and I have installed all the binaries
needed (using cmake and the module bundleUtilities) in this directory :
E:/projects/Alpha/installNow, I want to generate a NSIS package with cpack but
I have the following error when building the PACKAGE target
Am 09.04.2013 16:29, schrieb Clinton Stimpson:
How are the config settings and binary path for CTest already given
in the
CMakeLists.txt file? Normally, a CMakeLists.txt file does not have a
hardcoded binary path, nor does it have fixed config settings.
Wrong wording, sorry. They are, after
On Tuesday, April 09, 2013 04:11:06 PM Martin Baute wrote:
> I realize I haven't been all that clear about my intentions.
>
> I want to keep the amount of configuration files at a minimum.
> Lots of the information that is required for CTest (like config
> settings, source path, binary path etc.)
The CMake 2.8.11 release candidate stream continues!
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced Target Usage Requirements
- Targets can specify usage requirements for their consumers s
I realize I haven't been all that clear about my intentions.
I want to keep the amount of configuration files at a minimum.
Lots of the information that is required for CTest (like config
settings, source path, binary path etc.) or CDash (server address,
project name) are already given in CMakeLi
Hi there,
one thing I haven't been able to figure out yet. Quite
obviously the idea is that CMake, CTest and CDash should
go hand in hand.
But documentation-wise, there is a big rift once we are
done digging through the CMake docs. We are told that
"include( CTest )" in CMakeLists.txt does add C
It wouldn't. That's why your devs would have to agree to use it...
On Apr 9, 2013, at 9:36 AM, Petr Kmoch wrote:
> I was thinking about using a wrapper script for my case as well. How would
> this work with CMake automatically re-running when it detects a change in
> CMakeLists?
>
>
> On Tue
I was thinking about using a wrapper script for my case as well. How would
this work with CMake automatically re-running when it detects a change in
CMakeLists?
On Tue, Apr 9, 2013 at 3:33 PM, David Cole wrote:
> If all your devs agree to use it, you could just write a two-line wrapper
> script
If all your devs agree to use it, you could just write a two-line wrapper
script: call CMake on line 1 and your perl script on line 2...
On Apr 9, 2013, at 8:51 AM, Petr Kmoch wrote:
> Hi.
>
> Just for context: I've filed a request for generic support for
> post-generation commands some time
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=13020), but it was turned down.
So apparently a CMake C++ patch that would incorporate what your Perl
script currently does would be the way to get
Hi,
Im trying to use CMake (version 2.8.10) for a Fortran project with Visual
Studio 10
and Intel Visual Fortran Composer XE 2011. But the generated VS solution and
project file seems to have trouble in correctly determine the dependencies of
Fortran 90 files/modules when m4 preprocess envol
16 matches
Mail list logo
