On 8. Apr, 2010, at 3:39 , Ryan Pavlik wrote:
> You might consider just setting the EXCLUDE_FROM_ALL property on specific
> targets, instead of an entire subdirectory.
>
> Ryan
>
> On Wed, Apr 7, 2010 at 8:33 PM, Daniel Nelson wrote:
>
>> If I use add_subdirectory with the EXCLUDE_FROM_ALL op
You might consider just setting the EXCLUDE_FROM_ALL property on specific
targets, instead of an entire subdirectory.
Ryan
On Wed, Apr 7, 2010 at 8:33 PM, Daniel Nelson wrote:
> If I use add_subdirectory with the EXCLUDE_FROM_ALL option, then any files
> whose install commands are in that direc
If I use add_subdirectory with the EXCLUDE_FROM_ALL option, then any files
whose install commands are in that directory are not installed as part of
'make install'. Is this on purpose, and if so is there a way I can install
these files?
--
Daniel
___
Thanks, David. With that option we were able to understand that our homemade
tooling that has to force a specific option for the files compiled internally
by CMake needed tinkering to notice the new names (it's been so long since I
wrote the tooling that I'd forgotten about it!).
From: David Co
Hi,
I am including a thirdparty msproject with the include_external_msproject()
command. But this project has different configurations than the standard cmake
configs.
The mapping is like this:
CMake External Ms proj
-
> I’m trying to cross compile for ARM with this command:
>
>
>
> cmake . -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_TOOLCHAIN_FILE=arm-gcc3.4.5.cmake
>
>
>
> Here is my toolchain file:
>
>
>
> INCLUDE(CMakeForceCompiler)
>
>
>
> # this one is important
>
> SET(CMAKE_SYSTEM_NAME Linux)
>
> s
Thanks Yegor!
That solved my problem.
-Messaggio originale-
Da: Yegor Yefremov [mailto:yegor_s...@visionsystems.de]
Inviato: mercoledì 7 aprile 2010 17.00
A: Luigi Grilli
Cc: cmake@cmake.org
Oggetto: Re: [CMake] Crosscompiling for arm linux on cmake 2.8.0
> I'm trying to cross compile f
I'm trying to cross compile for ARM with this command:
cmake . -DCMAKE_BUILD_TYPE=DEBUG
-DCMAKE_TOOLCHAIN_FILE=arm-gcc3.4.5.cmake
Here is my toolchain file:
INCLUDE(CMakeForceCompiler)
# this one is important
SET(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR arm)
#this o
People have been known to use symlinks to solve the problem. There is
the BundleUtilities that help package the .app part. I wrote some
cmake code to do basically what you ate wanting to do. It is a
variation on the BundleUtilities code but works with an executable
outside of an .app bundle with li
On 7. Apr, 2010, at 13:26 , Christoph Höger wrote:
> Hi all,
>
> here comes the testcase:
>
> project(cmakeBug)
>
> set(src ${PROJECT_SOURCE_DIR}/src)
> set(inc ${PROJECT_SOURCE_DIR}/inc)
>
> add_custom_command(OUTPUT ${inc}/test.h ${inc}/test2.h ${src}/test.c
> COMMAND echo "//
On 7. Apr, 2010, at 12:40 , Frank Stappers wrote:
> Hello,
>
> Currently, I have a problem with linking to dynlib outside a bundle.
> Let me explain: We have a toolset that contains both unix-tools
> (applications without the .app suffix)
> and bundles (applications that have the .app suffix). A
Hi all,
here comes the testcase:
project(cmakeBug)
set(src ${PROJECT_SOURCE_DIR}/src)
set(inc ${PROJECT_SOURCE_DIR}/inc)
add_custom_command(OUTPUT ${inc}/test.h ${inc}/test2.h ${src}/test.c
COMMAND echo "//foo" > ${inc}/test.h
COMMAND echo "//foo" > ${inc}/test2.
Hello,
Currently, I have a problem with linking to dynlib outside a bundle.
Let me explain: We have a toolset that contains both unix-tools
(applications without the .app suffix)
and bundles (applications that have the .app suffix). After
installation, tools are installed in "./bin"
and shared lib
13 matches
Mail list logo