|
Notes |
|
|
(0010972)
|
|
Alex Neundorf
|
|
2008-03-28 20:29
|
|
CPACK_RESOURCE_FILE_LICENSE, CPACK_RESOURCE_FILE_README and CPACK_RESOURCE_FILE_WELCOME are handled the same way.
I guess if it is changed for CPACK_PACKAGE_DESCRIPTION_FILE it should be changed for these files in the same way.
Alex |
|
|
|
(0021593)
|
|
simonh
|
|
2010-08-02 10:18
|
|
|
Could we not check if the specified file is generated by the project? Can anyone point me at the relevant sources and I'll try to write a patch? |
|
|
|
(0021995)
|
|
Eric NOULARD
|
|
2010-08-28 11:08
|
|
Concerning the C++ code you can search for "GENERATED"
but this would apply to source file which were flagged as
"GENERATED". (cf set_source_files_properties).
I think this is used to source files attached to some target
(cmTarget --> cmTarget.[h|cxx])
but those files may not be seen in **any** target
so they won't be considered "source files" at all.
Now CPack.cmake may try to use "get_source_files_property"
for checking "GENERATED" but if the file is not a source file...
I don't really know if CMake knows the exhaustive list
of file that "will" be generated by add_custom_command
you may have to check the Source/cmAddCustomCommandCommand.cxx
in order check how it handles OUTPUT arguments. |
|
|
|
(0041419)
|
|
Kitware Robot
|
|
2016-06-10 14:27
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
|