I compiled R 4.1.0 from source on my Fedora 34 Workstation.
I had to install the X11 libraries to do so.
Is there a way to enable Wayland, so that it renders on Wayland directly?
I am also having problems with X11, see here.
Related
I want to run a program which needs Qt5.8 libraries, and the underlying OS is Ubuntu 14.05.5 LTS
This OS seems to include a prebuilt package for Qt 5.2.1 and nothing later in the repos.
Can I safely add Qt5.8 libraries? How would I do so? (I can only find instructions for installing the full Qt IDE)
As per my information, Binaries (or offline/online installers) for installing Qt (>= 5.6) on 32-bit linux are not provided. For example, If I want to use Qt 5.9.0 on 32-bit linux (debian, specifically), the only option is to download Qt source and build it. I have successfully built Qt 5.9.0 on my 32-bit linux machine. But I have to do this on all my development PC's. Instead if I can build it once and create an installer somehow, that will save a lot of time. Is there a way to create offline installer (e.g. *.run files) for installing Qt 5.9.0 on 32-bit Linux (e.g. debian)?
As stated by #Velkan, Qt is available on 32 bit Debian from the official repos.
But, indeed, there is no 32-bit Linux installer from the Qt project.
Regarding copying a Qt install from a Debian PC to another, you do not need to create an installer. Just copy/tar/zip the directory in which Qt is installed. The only requirement is that you must keep the installation in the same absolute path as the Qt Core library has the path hardcoded in it and it is use for plugin detection.
NB1: It is possible to patch Qt Core library to change the hardcoded path and even make it relative. It is not officially documented but you can take a look in the sources of tools like windeployqt or the online installer
NB2: Do not use Qt 5.9.0, prefer 5.9.2. Both are forward and backward binary compatible, but the latter received bug fixes.
I have a real problem with Unicode in Windows. So I just use Linux. Now I want to know if there is any innovative way to use Microsoft R Open which is installed on Linux bash as the interpreter in RStudio in Windows 10.
I know I can install an X Server on Linux bash but I want it to work in native Windows application.
Maybe this video is needed for inspiration.
Have smart minds any idea?
It is now possible to run RStudio Server on Bash on Ubuntu on Windows by installing opencpu and RStudio Server.
Please follow https://www.opencpu.org/download.html instructions.
Tested on Windows 10 Build 16299 with
opencpu-2.0 and rstudio-server-1.1.383-amd64
Install RStudio with conda, and stick to the Anaconda channels. They use MS Open R.
See also:
https://www.guru99.com/download-install-r-rstudio.html
I am trying to compile the development version of R under OSX, but I cannot find the correct way to link to the X11 libraries. I think they are included in XQuartz, but linking to /opt/X11/lib or /opt/X11/include/X11 using ./configure --x-libraries still generates an error that the headers cannot be found.
What is the correct way to link to the X11 headers with a default XQuartz install?
The X-specific options are both required ./configure --x-libraries=/opt/X11/lib/ --x-includes=/opt/X11/include worked fine.
I created a development environment with Fedora 18 and Qt 5
When I compile my app it will be 64 bit, and depend on Qt 5. After some research it seems that will be a problem since Centos 6.x is still dependong on Qt 4.6, and Centos 5.x is dependant on earlier Qt, and I'm guessin Ubuntu has its own package limitations.
Is there a "safe" version of Qt I can compile against to ensure it runs everywhere? If not, how can I expect customers to run my program?
If you want to target Linux, then I would recommend using Qt 4.8 (available on most of the Linux Distros), forget about Qt 5 for a year or so. Hardly any Linux distro other than Ubuntu 13.04 and above comes with Qt 5.
Secondly, as far as compiling is considered, if you wish to target Linux distros other than Ubuntu and Fedora than never use Ubuntu or Fedora for compilation. These are bleeding edge Linux distros which include new libraries without much testing. You will not only face the problem of old Qt versions in some Linux distros as you will face the bigger problem of glibc (C library). Make sure the Linux distro you use for compilation has a minimum possible glibc version for Qt 4.8, otherwise even if any Linux distro has Qt 4.8 installed, but has a lower version of glibc, you app still won't run. You can check out distrowatch.com to find out glibc and Qt versions for any Linux Distro
Example:
I compiled my app on Ubuntu 12.04, Qt 4.8.1 with glibc v 2.16 (perhaps). I got a bug report than application does not run on CrunchBang which also has Qt 4.8.1 available but since it is a Debian unstable Linux Distro it uses glibc v2.13. Since that day I always compile my application on CrunchBang (very lighweight, you can Virtual Box for this) and hardly some one complains now.
As far as CentOs is considered, you will need to recompile your code on CentOS.