Hi Rob,
What about:
if( NOT USE_SYSTEM_FOO)
# Build my own FOO
endif()
Hth
Jc
On Wed, Jan 29, 2014 at 7:09 PM, Rob McDonald wrote:
> I feel like this is a really dumb question, but I've got myself wrapped
> around the axel
>
> I'd like to use a negative conditional on a variable that
I feel like this is a really dumb question, but I've got myself wrapped
around the axel
I'd like to use a negative conditional on a variable that may or may not be
defined... say USE_SYSTEM_FOO
So, I'd like to do something like this...
IF( NOT ${USE_SYSTEM_FOO} )
# Build my own FOO
ENDI
Ok. Thanks for the help! I'll take a look at bug #14353 as I have time.
On Wed, Jan 29, 2014 at 2:13 PM, Stephen Kelly wrote:
> Steven Wilson wrote:
>
> > "\$<1:strip" -u -r customcommandtest>
> >
> > Note the "\$<1:strip" -u -r customcommandtest> output from the generator
> > expression.
>
Steven Wilson wrote:
> "\$<1:strip" -u -r customcommandtest>
>
> Note the "\$<1:strip" -u -r customcommandtest> output from the generator
> expression.
>
> What do I need to change in the POST_BUILD custom command to make the
> generator expression work correctly?
The generator expression stops
Consider the following CMakeLists.txt file (on a Mac, 10.9.1, Xcode 5, Unix
Makefiles generator):
cmake_minimum_required(VERSION 2.8.12)
project(CustomCommandTest)
add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/test.cpp
COMMAND echo "#include " > ${CMAKE_CURRENT_BINARY_DIR}/test.cpp
COMMA
The way source groups are sorted in Xcode seems off.
Here’s a sample file (using v2.8.12):
cmake_minimum_required(VERSION 2.8)
project(SourceGroupTest)
set(SOURCES
./Zebra/file.c
./Snake/file.c
./Dog/file.c
)
source_group(Snake REGULAR_EXPRESSION "Snake/.*")
source_group(Zebra REGULAR
Hi,
I’m experimenting with using Cmake’s bundle support on OS-X for a project. (Up
until now I have assembled the bundle by hand using a separate script which
also creates the DMG). I have the situation, that I need the executable name to
be different to the bundle name. MACOSX_BUNDLE_BUNDLE_NA
Looks like the right download page was
http://cmaketools.codeplex.com/releases/view/117807
Installing now.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community.
On Tue, Jan 28, 2014 at 2:32 AM, David Golub wrote:
> I just put out the first release candidate of CMake Tools for Visual
> Studio 1.1. This release will add support for CMake 2.8.12 and Visual
> Studio 2013. It also contains a number of minor enhancements and bug
> fixes. It is available for