Thanks for the explaination. I added the files to the target list as suggested by Filipe, and it worked. It is nice to know this is the proper way to do it.On 8/28/06,
Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> No, since it is a dependency of a source file that is included in the> e
Doug Henry wrote:
> No, since it is a dependency of a source file that is included in the
> executable I would expect it to be handled (it was in previous
> releases). It seems that cmake does know about it, because it gives an
> error with the correct path to the file that needs to be generated.
No, since it is a dependency of a source file that is included in the executable I would expect it to be handled (it was in previous releases). It seems that cmake does know about it, because it gives an error with the correct path to the file that needs to be generated. I don't know why cmake wi
Doug Henry wrote:
> Something about the custom command behavior has changed slightly and I am
> hoping I am just missing something. I have been able to do the following in
> the past:
>
> #
> # reswrap log.sql file
> #
>
> SET(DBNAME log_sql)
> SET(DBS ${PROJECT_BINARY_DIR}/${DBNAME}.h)
> SET(LO
Something about the custom command behavior has changed slightly and I am hoping I am just missing something. I have been able to do the following in the past:## reswrap log.sql file#SET(DBNAME log_sql)
SET(DBS ${PROJECT_BINARY_DIR}/${DBNAME}.h)SET(LOGSQL ${PROJECT_SOURCE_DIR}/../data/log.sql)ADD_
