Bug #18006 2011-03-17 01:37

austin_hastings

Custom build property disabled for generated files.

Using released 10.05 version, on Win XP/Pro SP3 en-us

I have a set of code-generation targets (lexer, parser) that I have supported with compiler properties/file-extension settings.

This works, in that the output files (C++ source) generated by flex/bison are added to the "Auto-generated" source folder.

But, like a lot of auto-generated source code, the generated files are chock full of warnings. Since I prefer to run with a high warning level (and -Werror), these files cause a huge bolus of warnings in the build logs, that I have absolutely no control over.

I would like to attach a custom build property to the generated files, reducing or disabling the warning settings for those files only. Something like

$compile $options -Wno-all -c $file -o $object

But the custom build property for the flex and bison sources control the first program (flex, or bison) to be run.

Trying to add the custom build property to the generated .cpp files fails, because the system knows these are generated files, and so it grays out all of the custom build dialog box.

My experience with generated source code suggests that this kind of thing is common - the generated files are always full of unused vars, unreachable code, etc. So I suggest that custom build properties should definitely be available for the generated files.

Category

Application::Interface

Group

 

Status

Open

Close date

 

Assigned to