10-30-2024 06:49 AM
I have a large LabVIEW project that contains RT and FPGA code, which I have continuously developed for many years.
I first develop the code to run on cRIO-9074, but I have included Conditional disable structures, so that code can also run on cRIO-9067 and cRIO-9057.
I have 3 LabVIEW projects, one for each target type and I copy my code changes (folders containing VI's and controls) from one project to another.
My method works, but please can anyone advise on a better way to manage the code to run on different target types.
I would prefer to have just one copy of the code files, so I do need to copy my code changes from one project to another.
Solved! Go to Solution.
10-30-2024 07:53 AM - edited 10-30-2024 07:56 AM
I have multiple times in the past have a single project with multiple targets in it for different cRIO chassis. Code that can be used with both host and RT is in a shared subfolder, then there is a host subfolder for VI’s only used in the host application and another for RT and one for FPGA.
It’s important to enable the “separate compiled code from VI” option for all VIs, libraries etc!
10-30-2024 08:04 AM
Where would the shared sub folder appear in the project tree?
Do you have this shown under both targets?
11-02-2024 09:50 AM
Yes I add it under each relevant target. That can give a bit of a difficulty if it contains a class or lvlib as they frequently end up getting locked when referenced from multiple contexts. I would recommend to keep development of such components on a separate project for that reason and use them mostly as ready made libraries only.
11-07-2024 04:06 AM
Thanks Rolf, I can try that.