01-29-2021 01:03 PM
My LabWindows 2017 project has hundreds of files so recently I tried to organize them into subdirectories such as:
/src -- .c source files
/inc -- include files
/uir -- user interface .uir files
LabWindows built with no changes (I expected I'd have to specify the search locations for include files, like with Eclipse and such).
But, today I realize any time I edit a .uir panel, it creates a brand new .h file in the /uir folder where the panel is.
Is there any project setting in CVI 2017 that would let me tell it where to write the generated header files?
Thanks, much.
01-30-2021 12:57 AM
No luck! There is no way to have CVI save the include file associated with the .UIR in a folder other that the .UIR folder!
On the other hand, that include files serve only to compile the project and you'll very rarely or never open them for anything...
01-31-2021 01:08 AM
I ended up making a Build Step that would copy them into my /inc folder... Not the best approach, since if someone edited a UIR and then checked the file back in without doing a build first, it would not be checking in the new file.
I expect I will go with having Panel .uir files and their related .h files in the same folder, and let my /inc be just for the ones we created. (Auto-generated versus programmer generated, I suppose.)
Thanks...