On 09/22/2011 01:24 PM, Rolf Eike Beer wrote:
>> Il 22/09/2011 10.13, Rolf Eike Beer ha scritto:
>>>> Yeah, that's exactly what I had in mind. Any chance that we will see
>>>> this in a future release?
>>> This is usually "find someone who does it and writes tests for it".
>>> Which
>>> then boils down to find someone who has enough knowledge and spare time
>>> to
>>> do or someone that needs it and is willing to pay Kitware for doing it.
>
>> Why don't you invoke ${CMAKE_OBJCOPY} as a post build command?
>
> That would be a way to _get_ these debug symbol files, but not a clean way
> to _install_ them. And the other reason is that this variable doesn't show
> up in any CMake documentation.
>
> Eike
In order to take up Andrea's suggestion for Lukas' concern:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(DEBUGINFO C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c "int main(void){return 0;}\n")
ADD_EXECUTABLE(main main.c)
FIND_PROGRAM(OBJCOPY objcopy)
ADD_CUSTOM_COMMAND(TARGET main POST_BUILD
COMMAND ${OBJCOPY} --only-keep-debug
$<TARGET_FILE:main> ${CMAKE_BINARY_DIR}/main.dbg
COMMAND ${OBJCOPY} --strip-debug
$<TARGET_FILE:main>
COMMAND ${OBJCOPY} --add-gnu-debuglink=main.dbg
$<TARGET_FILE:main>
)
INSTALL(TARGETS main RUNTIME DESTINATION bin)
INSTALL(FILES ${CMAKE_BINARY_DIR}/main.dbg DESTINATION bin)
This exemplary project simply follows objcopy's manpage
w.r.t. the --only-keep-debug switch and works on *nix.
Does it not work for you, or is it not clean enough?
Regards,
Michael
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
