User forums > Using Code::Blocks

Best way to integrate an "Other" file

<< < (3/3)

burtbick:
I've tried both ways.

That is I removed them from the Project and just let them appear as generated files.

And I tried it with not in the generated files and added back to the project.

No difference either way.

Thanks,
Burt

burtbick:
One other wrinkle.

I have two projects which are sharing the same protocol file.  A Server application and a Client application.
Using the Advanced setting option unfortunately applies the protocol compiler to both projects, and for the Client project I need a different macro to set a path to the protocol file that lives in the Server project's source / project directory.

What would be great would be a per project option that would work to build like the Advanced option solution.

I know about the file properties setting to use a custom compiler and I was using that before, but I wasn't able to get it to only compile the protocol file when changes were made.  Maybe that approach is better if I can get the file to only be compiled when a change is made to it.

Of course for that to work I need to include the generated .C and .H files in my project which isn't a big deal as long as the protocol compiler runs to create them.

Thanks,
Burt

Navigation

[0] Message Index

[*] Previous page