LV 2013 - More PPL madness.
I'm building an addon system, where the user can make addon pieces that are recongnizeable by my host piece and have them work together.
I am moving some of my code into PPLs (Packed Project Libraries) in order to make that code available both to the main host and to these addons.
I have a control called "Units". It's an ENUM with values like "degC", "degF", "degR", "N-M", "Ft-Lb", etc., etc. Since it's used everywhere and might be useful in the addons, I moved that control and the code that goes with it (units conversion, etc) into a PPL of its own.
Fine.
I have another PPL that manages channel selectors. It sorts the list of channels alphabetically or by hardware type, or by cal date, and manages the pop-up menu, and manages a units indicator that is associated. (If you switch to watching a temperature channel, for example, it switches the associated indicator to "degC".
So, it uses the UNITS indicator from the first PPL.
I discovered an error in my structure - the ChanSel manager uses the UNITS indicator from my Units LVLIB (the original), not the one from the units PPL. As a result, there are lots of coercion dots when I use the ChanSel manager, because the units I feed it from outside are the copy from the PPL, but it uses the original LVLIB copy.
So, I changed the ChanSel manager to use the UNITS control from the PPL.
But now, it complains when I BUILD the ChanSel manager: "Cannot Build the application because the folllowing source files are in the destination directory. You must build the application to a different directory from the source files", and it refers to the UNITS ppl.
I understand that it uses the UNITS PPL as a source file, but what is the problem with having a source file in the same folder as a dest file?
And then it gets even more maddening: if I put all the PPLs (I have about 15 now) in individual folders, then the build process will COPY the UNITS PPL into the same folder that it builds the ChanSel Manager PPL in! In other words, it does itself exactly what it complained about me doing.
And, on top of that, when it's time to open the project that USES them, it now will complain that there are TWO copies of the UNITS ppl and it doesn't know which one to use where.
Is there any sense behind this? If so, shine a light on it, please.
Do I have to make a post- build action to put them where I want them?, or is there a Don't-be-so-dang-stoopid option I can turn on?