On Thu, Jan 15, 2009 at 1:29 AM, Robert Dailey rcdai...@gmail.com wrote:
On Wed, Jan 14, 2009 at 11:23 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
I would try the following just to make sure it will find the library:
find_library(TBB_LIBRARY
NAMES tbb
On Wed, Jan 14, 2009 at 11:51 PM, Robert Dailey wrote:
On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva wrote:
On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
On 14.01.09 15:45:53, Robert Dailey wrote:
On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
If you
On Thu, Jan 15, 2009 at 12:15 AM, Philip Lowman wrote:
On Wed, Jan 14, 2009 at 10:54 PM, Robert Dailey wrote:
snip
It's not the only one. There are many modules that lack _LIBRARIES.
Somebody needs to fix them all but there is some confusion over how
_LIBRARIES works that needs explaining
Hi, I've been playing with imported targets and one *feature* surprised
me. The documentation states that an imported target is visible in the
current directory and below. What is the rationale for this behaviour?
It seems to be different from regular targets, where it can be
referenced everywhere
Ted Berg wrote:
I have been tasked with converting an existing Visual Studio project
2008 to CMake 2.6.2. The stumbling block is that this project uses a
precreated manifest file, which is included in an .rc file.
When the target links I get the following error:
CVTRES : fatal error CVT1100:
Rodolfo Schulz de Lima escreveu:
me. The documentation states that an imported target is visible in the
current directory and below. What is the rationale for this behaviour?
After some testing, the documentation is misleading. Actually cmake does
the right thing, it's possible to reference an
OK, thanks for the explanation.
It's rather clear now that this is probably not the way to go for me.
Exported targets might be a solution...
Regards,
Alexandre
--
A computer scientist is someone who fixes things that aren't broken.
-Original Message-
From: cmake-boun...@cmake.org
I tried with the standard gmake 3.81 that I compiled on .net 2003 with
support for an old MKS sh.exe that we already own (define HAVE_MKS_SHELL
in the config.h.W32), but can't get it working in parallel. Maybe sh is
too old too.
We'd rather avoid cygwin, as it's not simple to install once and
On Thu, Jan 15, 2009 at 4:03 AM, Hendrik Sattler p...@hendrik-sattler.dewrote:
It is kind of odd to test for the generator when the choice in fact depends
on
the compiler! What about e.g. Nmake?
Well the TBB libraries are set up in such a way that they depend on specific
versions of Visual
To look for the Compiler being used..
IF (MSVC60)
SET (...)
ENDIF (MSVC60)
IF (MSVC71)
SET ()
ENDIF(MSVC71)
IF (MSVC80)
SET ()
ENDIF(MSVC80)
IF (MSVC90)
SET (.)
ENDIF (MSVC90)
_
Mike Jackson
On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva
migu...@ieee.org wrote:
Well, I don't know about libfind_process, but none of the modules
shipped with CMake use it. Again your primary source of information to
properly write a find module should be the Modules/readme.txt
(
Alexandre Feblot wrote:
I tried with the standard gmake 3.81 that I compiled on .net 2003 with
support for an old MKS sh.exe that we already own (define HAVE_MKS_SHELL
in the config.h.W32), but can't get it working in parallel. Maybe sh is
too old too.
We'd rather avoid cygwin, as it's not
Ok Bill,
thanks for that detailled info. It will be really useful.
Regards,
Alexandre
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: Thursday, 15 January 2009 17:23
To: Alexandre Feblot
Cc: cmake@cmake.org
Subject: Re: [CMake] Pparallel build on multiple
On Thu, Jan 15, 2009 at 10:07 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
To look for the Compiler being used..
IF (MSVC60)
SET (...)
ENDIF (MSVC60)
IF (MSVC71)
SET ()
ENDIF(MSVC71)
IF (MSVC80)
SET ()
ENDIF(MSVC80)
IF (MSVC90)
SET (.)
On Thursday 15 January 2009, Robert Dailey wrote:
On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva
migu...@ieee.org wrote:
Well, I don't know about libfind_process, but none of the modules
shipped with CMake use it. Again your primary source of information to
properly write
On Thu, Jan 15, 2009 at 11:19 AM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Thursday 15 January 2009, Robert Dailey wrote:
On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva
migu...@ieee.org wrote:
Well, I don't know about libfind_process, but none of the
Brad King escreveu:
Really? That isn't intended, and I can't reproduce it. Can you provide
an example of this?
Sorry Brad, I did a more thoughtful test and cmake works according to
the documentation. In my previous test cmake was referencing directly
the library in /usr/lib instead of
On Jan 15, 2009, at 12:13 PM, Robert Dailey wrote:
On Thu, Jan 15, 2009 at 10:07 AM, Michael Jackson mike.jack...@bluequartz.net
wrote:
To look for the Compiler being used..
IF (MSVC60)
SET (...)
ENDIF (MSVC60)
IF (MSVC71)
SET ()
ENDIF(MSVC71)
IF (MSVC80)
SET ()
On Thu, Jan 15, 2009 at 11:30 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
I am not really sure about the ins-and-outs of Windows Dev but looking
through the Windows-cl.cmake file (Located in the
CMake-2.6.2/share/cmake-2.6/Modules directory) there are some variables that
you might
Funny. The following simple CMakeLists.txt file works as expected.
add_custom_command (OUTPUT Foo.txt
COMMAND echo Foo ${CMAKE_CURRENT_BINARY_DIR}/Foo.txt VERBATIM)
add_custom_target (Foo ALL DEPENDS Foo.txt)
Changing the .txt suffix to .exe however produces the following
Question:
Is there a way to set value for an environment variable, e.g. PATH, and let it
be valid in Makefile? ENV{XXX} can only be valid when cmake is runing, not for
make.
Reason:
Some commands depend on some environment varialbes.
Right now I'm trying to run omniidl to build corba idl
Michael Jackson wrote:
On Jan 14, 2009, at 1:27 PM, Clinton Stimpson wrote:
Bill Hoffman wrote:
Michael Jackson wrote:
Another reason to have a Drag-and-Drop installation for CMake. I
guess someone should file a bug for this.
If you want to create one, and contribute it that would be
Am Thursday 15 January 2009 18:13:43 schrieb Robert Dailey:
On Thu, Jan 15, 2009 at 10:07 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
To look for the Compiler being used..
IF (MSVC60)
SET (...)
ENDIF (MSVC60)
IF (MSVC71)
SET ()
ENDIF(MSVC71)
IF
So how does one use the cpack bundle generator with multiple applications?
I see the CPACK_BUNDLE_(NAME | ICON | PLIST | STARTUP_COMMAND) variables
I'm required to set, but that seems to only work when bundling one
application. And why doesn't it just pick up that information which I
had
On Thu, Jan 15, 2009 at 2:22 PM, Hendrik Sattler p...@hendrik-sattler.dewrote:
Am Thursday 15 January 2009 18:13:43 schrieb Robert Dailey:
On Thu, Jan 15, 2009 at 10:07 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
To look for the Compiler being used..
IF (MSVC60)
Robert Dailey wrote:
Check if CMAKE_SIZE_VOID_P is 8 (64bit) or 4 (32bit).
That seems random. The name also doesn't make any sense. Is there not a
more intuitive way?
The variable is CMAKE_SIZEOF_VOID_P, and it is documented:
Eric Lemings wrote:
Greetings,
How do you compile a .rc file into a .res file without linking it into a
library or executable?
Your paths and rc options may vary:
find_program( RC_EXECUTABLE NAMES rc )
set( BINARY_RES_DIR ${PROJECT_BINARY_DIR}/resources )
add_custom_command(
OUTPUT
Hi,
Currently I'm specifying include directories on a per-project basis. Suppose
I have projects A, B, and C. Project C would depend on A and B by specifying
A and B in a call to target_link_libraries(). Both projects A and B have
include directories that I set via a call to include_directories()
28 matches
Mail list logo