Hi all,
The following CMake script outputs "foo":
cmake_minimum_required(VERSION 2.8)
set(VAR foo)
message("@VAR@")
I'm surprised by this behavior, and could not find anything about it
in the documentation.
I'm also further confused by the parallell existence of the
string(CONFIGURE ... @ONLY@)
Hi,
> Date: Tue, 26 Feb 2013 20:25:42 +0100
> From: Stephen Kelly
> Subject: Re: [CMake] QT4 Module Patch Request
> To: cmake@cmake.org
> Message-ID:
> Content-Type: text/plain; charset="ISO-8859-1"
>
> Could you try this instead?
Yes, that works equally well!
Thanks,
Nicolas
PS: Sorry for th
Hi,
We're using CMake in a project that depends upon a custom-built Qt
version configured using -no-xmlpatterns.
We are currently using 2.8.10.2 without problems, but, because I
wanted to try the ninja support improvements, I downloaded the latest
nightly build for windows and gave it a run on ou
On Wed, May 23, 2012 at 11:29 AM, David Cole wrote:
> Regarding the loop swapping you ask about in your original post:
>
> I know we've discussed swapping those loops before on this list, quite to
> exhaustion.
I'm sorry to read that... now that I raised the topic again.
> The bottom line is:
On Wed, May 23, 2012 at 1:01 AM, Eric Noulard wrote:
> I'm not sure I understand, doesn't the
> -DCMAKE_FIND_ROOT_PATH:PATH=/Users/nt/Hacks/cmake-find-png/stage
> -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY:STRING=ONLY
> case gives you want you want:
Yes, I forgot to clarify that point. It does not work
Hi Cmakers,
I am trying to understand the VERBATIM option of the
ADD_CUSTOM_COMMAND CMake command.
Given the following macro:
macro (bogus_post_build target)
get_target_property(target_path ${target} LOCATION)
file(TO_NATIVE_PATH ${target_path} native_target_path)
add_custom_command(
Hi CMakers,
I have a CMake project where C and C++ sources are compiled and linked
in the same target (a static library).
The default setting of the generated Visual C++ 2005 projects is to
enable C++ exceptions for C++ code and disable it for C code (/EHsc,
see below).
However, I need to change
On Fri, Mar 28, 2008 at 4:45 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> I am guessing you would have to set those variables somewhere else for
> them to be in the system. I am not sure how a mac works, what
> environment does the windowing system run in? Can you set variables for
> that e
On Wed, Mar 26, 2008 at 6:12 PM, Alexander Neundorf
<[EMAIL PROTECTED]> wrote:
> Maybe using #ifdefs in the code ?
This could work, indeed, but is what I was trying to avoid :-)
Moreover, I'm CMake-ing an external project that I don't maintain,
which contains both (non-inline) x86 AT&T style as
Hi CMakers,
I gathered that setting this: CMAKE_OSX_ARCHITECTURES=ppc;i386 enables
universal binary building on MacOSX.
What I could not figure out, however, is how to specify different
sources list for a target, depending on the architecture being
compiled.
My goal is to include intel-specific
> This should work:
> SET(FOO_INCLUDES "@FOO_INCLUDES@")
It does, indeed.
Strange... I thought I had tried it already.
Thanks for your time.
--
Nicolas
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi all,
I am maintaining a build system for a project that uses a number of
external libraries whose sources are built with the whole project (ie:
not looked up in the host system).
Below is a trimmed down version of how the project is set up.
In that trimmed down version, libfoo is an external li
On Dec 21, 2007 3:19 PM, James Bigler <[EMAIL PROTECTED]> wrote:
>
> On Dec 21, 2007, at 7:09 AM, David Cole wrote:
>
> > What do you mean when you say LIB2 depends on EXE1...?
> >
> > Does EXE1 generate some code that is built into LIB2 or is it
> > something
> > else? Normally libs don't depend o
On Dec 21, 2007 2:33 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> You should create a small example that shows the problem, and attach it
> to a bug report.
It's here:
http://www.cmake.org/Bug/view.php?id=6193
--
Nicolas
___
CMake mailing list
CMake@
Hi,
I'm working on a C++ project that's been happily using CMake as a
cross-platform (mac/pc/linux) build tool for a year now.
We're using CMake 2.4.6 on all platforms.
Recently, some changes in our build system lead to the following
dependency graph:
LIB1 <- EXE1 <- LIB2 <- EXE2
^
15 matches
Mail list logo