Skip to content
  • Stephen Kelly's avatar
    file(GENERATE): Evaluate early to allow generating source files · b80557c7
    Stephen Kelly authored
    The evaluation files must be known before cmTargetTraceDependencies
    attempts to find them, but we must actually generate the files after
    cmTargetTraceDependencies, as that can add to target SOURCES.  The
    limitation is that the generated output name must not depend on the
    SOURCES of a target if the generated file is used by that target.
    
    Mark the output files as GENERATED so that trace dependencies does
    not expect them to already exist in the filesystem.
    
    Move the invokation of ForceLinkerLanguage in the Generate logic
    to after the generated file names are known.  ForceLinkerLanguage
    tries to determine the sources of a target (in order to determine
    an already-known language) and otherwise fails to get information
    about the generated file.
    
    Test that the output of file(GENERATE) can be used as a target source
    file and that accessing the target SOURCES in the name of the output
    file is an error.  Accessing the TARGET_OBJECTS would be a similar
    error if it was legal to use that generator expression in this
    context.  That is not currently possible and is a different error
    condition, so test the current error output as a reminder to change
    the expected output if that becomes possible in the future.  Test
    that generated rule files resulting from cmTargetTraceDependencies
    appear in the SOURCES generated in the output file.
    b80557c7