Am Wednesday 28 July 2010 schrieb Óscar Fuentes:
> Eric Noulard
<eric.noul...@gmail.com>
> writes:
>
> [snip]
>
> > if you need build
> >
time creation of the file then you may write a CMake script
> >
"generateMyFile.cmake" which contains such commands and use
> >
> >
add_custom_command( ...
> >
> > COMMAND ${CMAKE_COMMAND} -P
generateMyFile.cmake
> >
> > ...)
>
> That approach justs shifts
the problem to a separate cmake script, but
> it still remains.
>
> The
task here is to write a literal string containing a "special"
> character
(#) to a file, at build time. For "cmake -E echo" it requires
>
platform-dependent escape sequences. My idea about the cmake -E commands
>
was that they purpose is to abstract platform differences, but seems
> that
that is not entirely correct, as they inherit some traits from the
>
underlying platform. Or is it a bug?You do only need to escape things from CMake's own file processor as this is started from within the CMake build process. No need to call "cmake -E" at all. Eike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
