Use of PPLs in RTEXE

[CoastalMaineBird]

LV2013, LVRT2013

Small little test program, testing how to startup correctly in an RTEXE (running on PXI-8196):

If I run the above from the DevSys (click on RUN arrow), it works just fine.

If I remove the ROOT FOLDER vi, and build an RTEXE out of it, set it to RUN STARTUP and reboot, it works fine.

As shown, if I Build an RTEXE, set it to RUN AS STARTUP, it does NOT run.

No idea what happens, but it does not create the file.

No error message on the console, or anywhere else I can see.

That ROOT FOLDER vi is well proven, being in my toolbox for years. 

The key point (I think) now is that that VI is in a PPL (.lvlibp).

I tried making a separate PPL with just this one VI in it - still no joy.

(I've seen cases where a windows-only VI inside a PPL would prevent the whole library from working on LVRT ).  But that's not it here.

In the DevSys, I've used the same VI from the PPL on both the host (Windows) and the RT box (PharLap OS).

But not so, from an RTEXE.

How do I find the problem?

[CoastalMaineBird]

The VI in question uses nothing but primitives. No further VI calls, no Typedef controls, just primitive code.

[CoastalMaineBird]

Hmmm.

When building the PPL, I've been building it under the MY COMPUTER section.  I want to use the PPL on both the host and the RT box.

If I build this PPL under the TARGET box, then the startup test works.

Why is that?

Maybe under the DevSys, things are recompiled on the fly as needed, but once built into a PPL, it's fixed?

I can still use the PPL in the host side on WIndows, but maybe it's recompiling there.

Does that mean I cannot share a PPL between RT and Windows?

Is EVERYTHING that way, or did I manage to pick out one of the few that has to be recompiled?

I need to try a host EXE using this PPL to see, I guess.

Are the rules for this explained somewhere?

[CoastalMaineBird]

OK, I've proved it again: if I compile the PPL from the MY COMPUTER section of the project, it does NOT work on RT, but DOES work on the host.

If I compile the PPL from the RT TARGET section, it works on both sides.

Can anyone explain that to me?

[CoastalMaineBird]

This doc says something interesting:

If a VI calls a packed library on one target and you open the VI on another target, when the VI calls the packed library, the library tries to open on the original target.

Does that mean what I think it means?

When the RT program was trying to open the PPL, it tried to open it ON THE HOST?

That seems weird.