Page 1 of 1

Way to differentiate generated source files

Posted: Mon Jul 12, 2021 1:23 pm
by Jarod42

Using custom Makefile rules to generate source (as .yy -> .cpp),
the only way I found to use those generated files is to add them in project too.

  • I am wrong?
  • Is there a way to "mark" them (visually) as generated?

Re: Way to differentiate generated source files

Posted: Wed Jul 14, 2021 9:52 pm
by eranif

whats the purpose of marking them?
You dont want them to appear in the workspace tree?


Re: Way to differentiate generated source files

Posted: Thu Jul 15, 2021 6:01 pm
by Jarod42

Some context:
I'm testing/fixing premake with custom rules which were not implemented for Codelite/CodeBlocks generation. (patch already applied :-) )

  • In CodeBlocks, only source file (.yy) should be in project tree. and per file rule should create the obj file.
  • In Codelite, source file and generated file should be in project tree (or I miss a way to avoid that).
    I didn't check Visual.

I saw 2 generations "methods":

  • traditional way: generate the whole file
  • generate only regions of the file :-/

For the traditional way, initially, I don't want them in workspace tree.
But after reflection, I'm more mitigated:

All editions (by editor or Replace feature or similar) are problematic.
But for the "Find" features, there are cases where it is better to include them, and other to exclude them.
(and potentially for other features/plugins it is the same).

Potentially a show/hide generated files, but special icons or other graphical ways to differentiate them would be fine too.