How can I install multiple versions of the LabWindows Development Environment on the same machine? - labwindows

I develop software in LabWindows for multiple customers. Often it is the case that a customer is using a backlevel version of the CVI Run-Time Engine (RTE). When possible the customer is urged to upgrade to the latest, but when they can't I must build the software targeting the older RTE. LabWindows does not support compiling for previous versions of the RTE so the work-around is to install multiple versions of the LabWindows Development Environment, and compile using whichever matches the target RTE.
How can one install multiple versions on the same machine?

The LabWindows installer will not permit an older version to be installed on a machine which already has a newer version on it. To get around this, the LabWindows Development Environment must always be installed in the order of oldest to newest, with the oldest version installed first.

Related

Can we install OpenJDK-11 in Redhat Enterprise Linux-7.x O/S version

I am currently running my Java based applications with OpenJDK1.8 and RHEL [Redhat Enterprise Linux] - 7.9. I am planning to upgrade few of the Java native libraries into higher versions whereas I need to upgrade my Java version to OpenJDK11 in that case.
Can anyone suggest whether OpenJDK11 compatible with RHEL-7.9 ? I don't have a plan to upgrade my RHEL version into RHEL-8.x.

How to install specific version of Cap'n Proto (v0.8.0)?

sudo apt install capnproto
This installs v0.7.0 in my ubuntu 20.04. However, i require v0.8.0 to be installed.
Also, i need v0.6.1 to be installed additionally for backward compatibility.
Any solution for these two cases ?
You will probably need to install from source rather than use a distro package. Unfortunately, it sounds like the Ubuntu distro package hasn't been updated in a while.
Instructions for building and installing from source can be found here: https://capnproto.org/install.html
Old versions are available by changing the version number in the download URL to whichever version you need.
Note that all versions of Cap'n Proto are backwards-compatible, so there should be no need to install older versions, unless you need to run a specific complied binary that was linked against a specific old version.

Bigcommerce | Stencil - Why is the recommended node version for windows so old?

The Stencil pre-requisites page recommends only installing LTS versions of node, and the specifically recommends Node 4.4.0 for the Mac and 4.1.2 for Linux.
However for Windows the recommended version is 0.12.7 even though the current LTS is 4.4.5. Is there a particular issue on Windows with newer versions or is the documentation just outdated?
Those are the latest BigCommerce-tested versions on each operating system. You can try the current LTS, but issues may arise.

Why do Linux distributions ship outdated CMake versions?

Ubuntu shipped CMake 2.8 when version 3.3 was the current version. Other Linux distributions do it similar. Is there a reason like backwards-compatibility issues with CMake 3.0?
I found plenty of people willing to explain how to upgrade CMake to the latest version, but couldn't figure out why it wasn't done by default. I'd like to understand the mentality of keeping it back before I decide to override the decision and upgrade it myself.
Depends on the Linux distribution you're using. A distribution's maintainers cannot ship future versions and often they don't upgrade version with updates as it might break existing applications.
CMake 3.0 has some minor incompatibilities. More important, it got new features and some bugs were fixed. If software relys on these, you'll need a new version.
Btw: With CMake 2.8 the third part of the version number is relevant. They stayed a long time with 2.8.x and added features with increasing x. Then they could not update to 2.9 or 2.10, thus they decided to change the version scheme and increase y in 3.y.
Your question applies to a wider range of software. It is a general question, whether a distribution should stick to defined versions of software they provide or whether they should update it and potentially break the costumers' setup. Enterprise distributions like RHEL or SLE are very conservative and fix bugs for at least a decade. Ubuntu updates it distribution every six month but you can stick to the LTS for three years. Fedora even updates some key components like the kernel after the release. Arch Linux and openSuse Tumbleweed are rolling releases, the update their software almost on a daily bases, when the upstream updates publish new versions.

installing matplotlib on ubuntu?

I have:
Ubuntu 8.04
python 2.5.2 installed on this Ubuntu
matplotlib 0.92.0 installed
I want to upgrade to (atleast) matplotlib 0.99
so that I can do 3d plotting.
The synaptic package (also the command line apt-get)
tells me that whatever I have is the latest matplotlib (which is not true).
How can I install matplotlib 0.99 or matplotlib 1.0.1 ?
You have the latest available package version for your operating system. Given that Ubuntu is at version 11 now and you are using 8.04, the version difference in the matplotlib package might not come as very surprising.
As for installing the newest version, I'd suggest reading:
http://matplotlib.sourceforge.net/faq/installing_faq.html
...if all fails, you can always install from source.
Note that support for Desktop versions of 8.04 LTS is due to expire shortly -- if this is a desktop machine, perhaps the easiest answer is to upgrade to 10.04 LTS, 10.10, or the very-soon-upcoming 11.04 release (or whatever they'll call the next release). Maybe not "the easiest answer", but an answer that includes security updates for Mozilla, Adobe Flash, the Kernel, and so forth.
Many newer versions of packages are supported via the Ubuntu Backports facility, but I didn't spot python-matplotlib in the list of available packages. Perhaps they would provide it if you asked nicely, perhaps it would be too much work.
You can always try installing newer versions from newer releases, but newer versions of python and libraries might introduce worse problems. (But probably will work fine.) See the apt_preferences(5) manpage for details on how to configure multiple APT sources and select some specific packages from a newer distribution (pinning), and rely on the older distribution for all the other packages.
Jim's answer of building the version you need from source is probably your best second option, if installing a newer version of the distribution is too daunting / otherwise impossible at this point.