On 11/29/2010 6:52 AM, Michael Hertling wrote:
Perhaps, this is a good opportunity to ask a related question: Some
time ago, there has been an issue with special linker scripts which
are part of a project. Of course, one would like to see the linker
triggered when these scripts change, and the
Bill Hoffman bill.hoff...@... writes:
No need for all the complication...
If you already know where the library is going to be:
${CMAKE_CURRENT_BINARY_DIR}/kernels/libkernel_executable.a
Then link directly to the full path:
target_link_libraries(main_target
On 11/29/2010 05:05 AM, Bill Hoffman wrote:
On 11/28/2010 3:19 AM, Sebastian Schaetz wrote:
Michael Hertlingmhertl...@... writes:
1) In the top-level CMakeLists.txt, you might say
SET_SOURCE_FILES_PROPERTIES(
main.cpp PROPERTIES OBJECT_DEPENDS
Michael Hertling mhertl...@... writes:
1) In the top-level CMakeLists.txt, you might say
SET_SOURCE_FILES_PROPERTIES(
main.cpp PROPERTIES OBJECT_DEPENDS
${CMAKE_CURRENT_BINARY_DIR}/kernels/libkernel_executable.a
)
When libkernel_executable.a has changed, this results in
On 11/28/2010 3:19 AM, Sebastian Schaetz wrote:
Michael Hertlingmhertl...@... writes:
1) In the top-level CMakeLists.txt, you might say
SET_SOURCE_FILES_PROPERTIES(
main.cpp PROPERTIES OBJECT_DEPENDS
${CMAKE_CURRENT_BINARY_DIR}/kernels/libkernel_executable.a
)
When
Hi,
I have a somewhat weird setup to build binaries for the Cell processor:
|-- CMakeLists.txt
|-- kernels
| |-- CMakeLists.txt
| `-- kernel.cpp
`-- main.cpp
From the main.cpp in the root directory the executable is built.
In the kernels folder strange things (have to) happen: first the
On 11/26/2010 05:00 PM, Sebastian Schaetz wrote:
Hi,
I have a somewhat weird setup to build binaries for the Cell processor:
|-- CMakeLists.txt
|-- kernels
| |-- CMakeLists.txt
| `-- kernel.cpp
`-- main.cpp
From the main.cpp in the root directory the executable is built.
In
