On 02/10/2011 02:11 PM, Verweij, Arjen wrote:
> Thanks Tyler,
>
>> -Original Message-
>> From: Tyler Roscoe [mailto:ty...@cryptio.net]
>
>> You can't use add_custom_command() to drive this because the results of
>> any custom commands will only be available at build time. You need stuff
>
Thanks Tyler,
>-Original Message-
>From: Tyler Roscoe [mailto:ty...@cryptio.net]
>You can't use add_custom_command() to drive this because the results of
>any custom commands will only be available at build time. You need stuff
>to happen at CMake configure time.
I noticed. Add_custom_ta
On Wed, Feb 09, 2011 at 05:24:28PM +0100, Verweij, Arjen wrote:
> Currently there is a python script that does preprocessing of all
> source, stores information in override.cmake files using
> set_source_file_properties(). This works fine, but makes maintaining
> source more error prone than it was
Hi,
I'm looking for a way to parse information from source files and feed the
outcome as input to the build process.
In more detail, I have Fortran files that contain information about what
optimization flags should be fed to the compiler.
Currently there is a python script that does preproces
