05-20-2015 02:47 PM
Stephen, I don't think its a VIPM problem. looking at your post-install VI. It seems you are purposly making everything read-only. So...
05-20-2015 03:46 PM
Does the PostInstall.vi run before VIPM does its mass compile?
05-20-2015 04:02 PM
Yes, I'm pretty sure.
05-20-2015 04:30 PM
ARGH!!!
OK. That means that if we're going to turn on read-only, we have to turn on source-only. Or we have to not turn on read-only.
Any preferences? Clearly Mikael prefers to make the files read-only so users do not accidentally edit the templates. That makes sense. Is that enough reason to modify all the files to use source-only?
05-20-2015 04:32 PM
Or I could run mass compile myself over the VIs that are being marked read-only, but that only solves the short-term problem. It doesn't help with the force recompile for an F1 patch.
Any bets on what I would break if I turn on source only?
05-20-2015 05:54 PM
I've seen that the in some cases (if the files aren’t read only), that the class templates gets modified and start inheriting from your projects classes.
IS the option: skip mass compile after install="TRUE"
…still TRUE in these VIPs?
05-20-2015 05:56 PM
I've tried it, you just have to be patient the first time you start LV.
05-20-2015 06:19 PM
Patience is not a user strong suit. 🙂
OK. I just changed out the files on the Google Drive.
These two are built for the specific bitness of LabVIEW 2014
NI_GDS_2014_64-1.1.67.68.vip
NI_GDS_2014_32-1.1.67.68.vip
This one is the bitness independent "run mass compile and THEN apply the read-only setting" version:
NI_GDS_2014-1.1.73.73.vip
The specific bitness versions take about 5 minutes to install. The mass-compile-on-install version takes about 45 minutes to install (on my machine). Your mileage may vary.
I'm going to now submit these files to The Powers That Be to be made available through the LabVIEW Tools Network. These files will remain available on my Google Drive until the LTN is updated or Google kills the service, whichever comes first. 🙂
05-20-2015 06:52 PM
I agree: Patience is not a user strong suit.
That's why I have a precompiled version for all LV releases from 2012 - 2015 32 & 64 bit.
05-21-2015 09:47 AM
How do the 1.1.67.68 and 1.1.73.73 packages compare to the versions listed on GitHub. Are they based off the 1.0.37 (Master) or the "untested" 1.1.0.0 (Master) ? Are the numbers staying consistent between the two sites? From earlier posts it looks like it's the 1.0.37 but I wanted to be sure.