On 06/20/2015 04:10 AM, Roman Wüger wrote:
> but the problem with this command is, that for multi configuration
> environments (e.g. Visual Studio), it requires $ in the
> filename which then creates 4 header files. One for each configuration.
Yes, because generator expressions can reference thing
Hello Brad,
but the problem with this command is, that for multi configuration environments
(e.g. Visual Studio), it requires $ in the filename which then creates
4 header files. One for each configuration.
Maybe I didn't understand something, but after that I also need to call
configure_file
On 06/12/2015 07:19 AM, Roman Wüger wrote:
> It would be great if generator expressions can be used with
> configure_file to avoid such overhead.
>
> Does anyone have an idea on how to solve that?
See file(GENERATE).
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check
Hello,
short description: I want to have a configuration header file per unit test.
For this purpose I wrote the following function, which creates a header file
in ${CURRENT_BINARY_DIR} and copy all test files into the binary
directory.
Howewer, I got it to work when I use add_custom_tar
