It's a little obtuse but you need to use \${CMAKE_INSTALL_PREFIX} in that
first argument to fixup_bundle(). If you don't, ${CMAKE_INSTALL_PREFIX} will
be evaluated at CMake-time and therefore point to your build-time install
directory. You want to delay evaluation of that variable until CPack time,
On 03/15/2011 06:30 PM, arrowdodger wrote:
> On Tue, Mar 15, 2011 at 12:20 PM, Michael Wild wrote:
>
>> Just one warning: AFAIK these rule variables are only used for
>> Makefile-based generators, *NOT* for Xcode and VisualStudio and the
>> like. I'd prefer the route via add_custom_command/add_cu
Sure thing, it's attached.
Thanks,
Tim
- Original Message -
From: "Rolf Eike Beer"
To: cmake@cmake.org
Sent: Thursday, March 17, 2011 5:18:44 PM
Subject: Re: [CMake] FindHDF5.cmake patch
Am Donnerstag 17 März 2011, 21:55:11 schrieb Tim Gallagher:
> Hi,
>
> Our project uses HDF5 and Fo
Am Donnerstag 17 März 2011, 21:55:11 schrieb Tim Gallagher:
> Hi,
>
> Our project uses HDF5 and Fortran, and while I was looking through the
> comments in the FindHDF5.cmake file, I saw that it doesn't support finding
> the Fortran bindings. So, I modified it to make it work to find the
> Fortran
I'm trying to use CPack to create a .tar.gz package on linux. I use
fixup_bundle from the bundle utility to copy and fix Qt libraries to the
bundle.
When I use simple 'make install', everything is installed properly in
directory specified by CMAKE_INSTALL_PREFIX. When I use CPack, the Qt
libraries
Hi,
Our project uses HDF5 and Fortran, and while I was looking through the comments
in the FindHDF5.cmake file, I saw that it doesn't support finding the Fortran
bindings. So, I modified it to make it work to find the Fortran bindings.
Below is the diff output. Let me know if there's a more u
I am using 2.8.4 (on Fedora Core 13).
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent: Wed 3/16/2011 12:04 PM
To: Chatterjee, Shash
Cc: cmake@cmake.org
Subject: Re: [CMake] Eclipse generator - scanner-discovered include pathsand
pre-processor symbols
O
There is a very old, long-standing open bug (in the "backlog" now)
that outlines many of the issues related to supporting pre-compiled
headers.
http://public.kitware.com/Bug/view.php?id=1260
Doing a "copy and rename" strategy for StdAfx.cpp is a reasonable
work-around until such time as this ca
2011/3/17 Dixon, Shane :
> I want to add some messages at the end of cmake that display all the
> DEB-related variables and what they’re set to. I’d prefer to now shows
> these when building on windows where DEB isn’t available. Is there
> something like
>
>
>
> If(DEBIAN_FOUND)
This is not cu
> > Quick question.
> >
> > I am trying to add precompiled headers to a project that
> has been converted to use Cmake.
> >
> > In our library directory, we include all our source and
> build two targets (one static and one dynamic), but setting
> multiple source values only affects the source
On the contrary: as you can see by the number of bugs related to this
one's duplicate [ http://public.kitware.com/Bug/view.php?id=10257 ]
and by the number of people participating in those discussions, it is
quite common for people to encounter this problem.
See all the notes in the bug and its re
I haven't found a super-easy, completely reliable way to do this for
all versions of Visual Studio. But here's some data for you...
If it's set, for VS9 and earlier, CMAKE_MAKE_PROGRAM will point to the
full path of devenv.com:
CMAKE_MAKE_PROGRAM:FILEPATH=C:/PROGRA~2/MICROS~1.0/Common7/IDE/devenv.
Noone else experienced this problem?
/A
On Mon, Mar 14, 2011 at 4:37 PM, Anders Backman wrote:
> Im using CPack with CMake 2.8 and when I am installing my app, I get the
> message:
>
> Warning! PATH too long installer unable to modify PATH!
>
> Seems that Im not the first:
>
> http://public.kitw
I'm wanting to get a path that points me to where vcvarsall.bat might live.
It's usually in the VS installation directory, and I was wondering if there
was a nice convenient CMake variable that could tell me where Visual Studio
is located.
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcv
I want to add some messages at the end of cmake that display all the
DEB-related variables and what they're set to. I'd prefer to now shows these
when building on windows where DEB isn't available. Is there something like
If(DEBIAN_FOUND)
that I can use to determine if the deb packag
When you are running an install "SCRIPT" it is simply included in the
context of the file cmake_install.cmake. So you can reference
variables that are in use in the including file inside your install
SCRIPT file. Read through the contents of a typical
cmake_install.cmake to get more ideas about wha
On 28/07/2010 15:34, Brad King wrote:
On 07/27/2010 06:48 PM, Russell Harmon wrote:
We're looking to use cmake on a project which has some dependencies
which are not properly picked up by cmake's dependency scanner. I'm not
looking to fix the scanner, because I feel the scanner is fundamentally
Ok I finally got it to run. I've done it this way:
EXECUTE_PROCESS(COMMAND cmd /c regsvr32 test.dll
WORKING_DIRECTORY "C:/Program Files/test/lib"
OUTPUT_VARIABLE ov RESULT_VARIABLE rv
OUTPUT_STRIP_TRAILING_WHITESPACE
)
Works fine, but there is still the problem to get the target build
Well I tried looking at the code and found cmVS10LinkFlagTable.h was the
only file to mention MANIFESTUAC. But I can't figure out a simple fix. It
pretty obvious this entry in the table is way to simple:
{"UACUIAccess", "MANIFESTUAC:", "Enable User Account Control (UAC)", "",
cmVS7FlagTable::Us
-- Forwarded message --
From: John Drescher
Date: Thu, Mar 17, 2011 at 5:43 AM
Subject: Re: [CMake] Setting Build properties for VS 2008
To: Dan Furtney
On Wed, Mar 16, 2011 at 11:25 PM, Dan Furtney wrote:
> Is there a way for cmake to set the active build in a multi-project VS
20 matches
Mail list logo
