Relative Paths

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that code

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that code o

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that code to

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that code to monitor

[LuisG]

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably use some of that code to monitor when

[LuisG]

(Sheesh... I hate it when this happens)

JB,

Since you're planning on sort of automating the editing of the project file, you might want to look at this example:

  C:\Documents and Settings\All Users\Documents\National Instruments\CVI85\samples\dotnet\FileSystemWatcher

You can probably modify that example to monitor the file, such that when it changes, you can run your script to update the file.

About the path issue in general, you make a compelling case. For the next version of CVI, we'll definitely consider extending the relative-to-project criteria for all paths.

Luis

[Mohan]

If you control all the source files in your project, then instead of using "Include Paths" in CVI, you could also try using relative paths in the include directives, like:
#include "../../foo/foo.h"
This may be more maintainable and would work in all C compilers.