in another thread ("petition for NI to support C99", see (1)), wally_666 wrote:
"
The name collision in
the CVIBUILD.projectname between the Linux and windows versions is an
irratition when trying to maintian the Windows and Linux versions in
the same shared directory"
this brings up a new question: is there a way in the LabWindows/CVI IDE to configure the output directory for the intermediate object files as well as the resulting executable files ?
each time i create a new project, i hack through the project file to setup my own output directory (generally, a 'bin' folder under the project root). unfortunately, i have to set it up by hand since i can't find a way to specify this in the project settings. also, it only affect the location of the generated executable files, and i can't find any way to change the directory for the intermediate object files which generally goes into a 'cvibuild.xxx' folder (and will trigger the aforementioned name collision).
i admit that i am a little bit of a maniac: things should go where i tell them to go, everything must be organized. that's why i do always have a directory to hold all the project's source files, another directory to hold the resources (uir, icons, ...) and of course a directory for the output files. since i do compile many of my projects using 2 or more different compilers (each one is good at finding some specific errors), i also have a rule for where the object files must go, and CVI breaks my rule, which is kind of agacing. it also forces me to write specific rules for cleaning the project in my pseudo-make files (which really are batch files, see (2)).
(1) didn't you forget to answer the poll ? no, you did not, did you ? please, tell me you did not... if you did forget: please do answer the poll.
(2) did you know you can compile a CVI project form the command line ? this will make a good post for the tips'n'tricks section...
