This may sound a little convoluted...but there are many benefits and so I try...
I'm working on code modules that are used on both Windows and Linux RT (class based, Actor Framework). The desire is to keep one source code since the same functionality is used across many targets (we have lot's of cDAQ's and lot's of cRIO's and many reusable code modules). I want to use PPL's to protect the code and provide a simple interface to building applications. PPL's are compiled code specific to target OS. A child class points to a specific parent. That parent must be of the same OS, bitness, LV version, etc of the child class for it to work.
To create a code module from the same source but compiled into two different versions, I first copy the parent PPL of one type into a master directory. The child source points to the PPL in the master directory. Write code, test, then make a PPL build of that child. Then to create the child of the other OS type, I first overwrite the parent PPL in the master directory with the corresponding PPL of that type. I use a separate project and add the child source code to that project, under the new target type. I can then create a PPL for the other OS type. When creating builds, this process of copying the file to the "master location" can be automated with pre-build actions. The problem when developing code is that I have to make sure the appropriate PPL is in the master directory before I open the child class or vi's.
Hence the desire for some sort of "pre-project" vi or action that allows me to automate the process of copying (or verifying) the right PPL into the master directory.
