Support Relative Paths in Build Specs

[_carl]

At present, build paths in build specs are stored as absolute paths, unless the path happens to be in the same folder as the project. Relative paths that are a level or more up from the project folder are not supported. Modifying the XML directly does not support relative paths either.

When working on multi-developer projects, where source control root folders may be different, this can be a serious annoyance.  One of the better workarounds at the moment is to build to a non-desired relative path (within the project folder) and then to run a post-build action to move the generated files to the desired location.

But it shouldn't have to be this way -- relative paths should just work.  (They are supported elsewhere in projects, such as with dependencies.)

(Note: this is the follow-up to a post on the LabVIEW forum about the same issue.)

[_carl]

Actually the path stays relative as long as the destination directory is in the project folder (relative to "project") or one level higher (relative to "common").

---

And this is the issue -- there does not appear to be any way (short of trickery) to provide a relative path to something that is more than a level up.

This is a common and valid use case.  And without jumping through hoops, there is no way to do this. (I'd love to be proven wrong though.)

Modifying the XML does not work (LabVIEW fails to read it, and falls back to defaults).

Trickery is required (and the best option I've come across is a post-build action that moves code after it's build to a less-desirable directory).