On Thu, 7 Feb 2013 17:05:55 -0800, Ed said:
>I am trying to build an app to be compatible with Mac OSX systems 10.6,
>10.7, and 10.8 using the command line with cmake. I have successfully
>built it for 10.7.5, now I would like to expand this app to be
>compatible with 10.6 and 10.8 is this possib
Hello:
I am trying to build an app to be compatible with Mac OSX systems 10.6, 10.7,
and 10.8 using the command line with cmake. I have successfully built it for
10.7.5, now I would like to expand this app to be compatible with 10.6 and 10.8
is this possible?
This is the command I am issuing to
On Wednesday, February 06, 2013 01:09:20 PM Patrick Johnmeyer wrote:
> I have looked through the CMake wikis and several mailing list threads that
> the following google search returned, and I have not found a definitive
> answer to my question.
>
> [site:www.cmake.org/pipermail/cmake CPack multip
On Thu, Feb 7, 2013 at 12:41 PM, Yngve Inntjore Levinsen <
yngve.levin...@gmail.com> wrote:
> I think you are fighting the tool in any case, because you are asking to
> build multiple configurations in one build folder (?). Normally you would
> create one build folder per configuration.. Which I g
The approach suggested by Ansis looks interesting. Instead of using
"install(FILES ...), you could use CPACK_INSTALL_CMAKE_PROJECTS [1][2]. For
an example, see [3] and [4]
[1]
http://www.cmake.org/cmake/help/v2.8.8/cpack.html#variable:CPACK_INSTALL_CMAKE_PROJECTS
[2] http://www.cmake.org/Wiki/CMak
On 2/6/2013 6:00 PM, Theo Berkau wrote:
Hello,
I've been trying to setup a cross-compiled project using cmake and so
far everything's working fine using "Unix Makefiles" generator, etc. Now
I know generating for visual studio generally doesn't work under a cross
compiling setup, but I was wonder
Hi,
I think you are fighting the tool in any case, because you are asking to
build multiple configurations in one build folder (?). Normally you
would create one build folder per configuration.. Which I guess is what
you are doing today.
Instead of specifying the compile flags manually you can in
How about something like this:
if(${CMAKE_BUILD_TYPE STREQUAL DebugAndRelease)
include(ExternalProject)
ExternalProject_Add(MEDEBUG
CMAKE_FLAGS -DCMAKE_BUILD_TYPE Debug)
ExternalProject_Add(MERELEASE
CMAKE_FLAGS -DCMAKE_BUILD_TYPE Release)
install(FILES ...)
#et
On Thu, Feb 7, 2013 at 3:12 AM, Yngve Inntjore Levinsen <
yngve.levin...@gmail.com> wrote:
> Did you try to create two targets and add per-target compile flags?
>
>
What you suggest is replacing configurations with targets. That may be
possible, but runs counter to how CMake natively works. I fee
Did you try to create two targets and add per-target compile flags?
Something along the lines of
add_library(mylib_rel ${sources})
add_library(mylib_dbg ${sources})
set_target_properties(mylib_rel PROPERTIES COMPILE_FLAGS -O3)
set_target_properties(mylib_dbg PROPERTIES COMPILE_FLAGS -O0 -g)
Not e
10 matches
Mail list logo
