Every Path is absolute.
Any more suggestions?
On Tue, Mar 30, 2010 at 07:46:37PM +0200, Michael Wild wrote:
> Also make sure that all paths are absolute. Relative paths sometimes have
> strange effects in custom commands.
>
> Michael
>
> On 30. Mar, 2010, at 19:04 , David Cole wrote:
>
> > That would happen if hcparser.y were changed. Does that file also change? Is
> > it generated?
> >
> >
> > 2010/3/30 Christoph Höger <choe...@cs.tu-berlin.de>
> >
> >> Hi all,
> >>
> >> I have a buildsystem here for a project containing several subprojects. All
> >> those subprojects have their own CMakeLists.txt in a subfolder.
> >> One of those subprojects needs to run a script to generate some
> >> sourcefiles:
> >>
> >> add_custom_command(OUTPUT ${typesh} ${typesc}
> >> COMMAND ${binbash} ${PROJECT_SOURCE_DIR}/mosilac/mktypes.sh
> >> DEPENDS ${src}/hcparser.y
> >> WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/mosilac)
> >>
> >> This does work. As it does in other places. But in that single place I have
> >> a problem when working on other parts of the buildsystem:
> >> Whenever I change a CMakeLists.txt file subsequent make calls lead to a
> >> re-generation of the output files, although they're unchanged.
> >>
> >> Does anyone know why this happens?
> >>
>
_______________________________________________
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
