[CMake] big custom command dependency problem
Juan Sanchez
Juan.Sanchez at amd.com
Mon Aug 6 16:43:33 EDT 2007
I found the problem. The output from the custom command has to
explicitly specify the destination path of the output file.
OUTPUT ${PROJECT_BINARY_DIR}/output.cc
I was already specifying the full path for the input to the library.
Regards,
Juan
Juan Sanchez wrote:
> I created a custom command to generate a cpp file.
>
> I then use this cpp file to create a library as a separate add_library
> command.
>
> Whenever I type make, this cpp file is regenerated, and the library is
> recreated. Compiling this file is super expensive. Nothing has changed
> between invocations of make.
>
> I stated the dependencies in the custom command. Why is it always
> recreating the cpp file?
>
> Is there anyway to stop this behavior?
>
> Turning off dependency checking is not an option since it is needed for
> everything else. This is gmake on a linux box.
>
> Thanks,
>
> Juan
>
>
> _______________________________________________
> CMake mailing list
> CMake at cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>
>
--
Juan Sanchez
Juan.Sanchez at amd.com
800-538-8450 Ext. 54395
512-602-4395
More information about the CMake
mailing list