I work on a centOS 6.6 distro and would like to use Rstudio. I would like to use an up to date version say v>0.99 but from the download page I can see that Rstudio desktop requires RHEL7.
Looking for older versions of rstudio desktop I see that RHEL6 can only get v<=0.981103, though Rstudio server seems fine, and I am OK if many can use a server version.
rpm is a no go for me so is there a way to get the sources for the server version like they provide for the desktop version ? I can't find it anywhere but it appears it is possible: see this post.
Of course if there is a trick to build Rstudio desktop on centOS 6.6 I am a buyer...
You won't be able to build RStudio Desktop for RHEL6 because of a glibc requirement induced by Qt 5.4. This is not easily evaded so if you have a platform requirement for RHEL6 you'll want to stick with the server version.
The desktop and server versions of RStudio are actually built from the same source code. You can get the source for any RStudio release here:
https://github.com/rstudio/rstudio/releases
The make-package Server RPM command in rstudio/package/linux will start the build once you've got all the dependencies installed. See here for details (or INSTALL): https://github.com/rstudio/rstudio/wiki/Installing-RStudio-Dependencies
Related
I am trying to get the above development system working, I am starting with a Varicsite NANO compute module. I am trying to get QT 5 setup to develop. I have been unable to find a good Debian guide on how to do that. I would eventually want the QT application to run in kiosk mode without the Weston desktop.
I have Debian built using their instructions of building Debian for the IMX8 board. It runs fine Weston comes up on boot.
I have installed the following packages on the target device.
sudo
apache2
php
jq
curl
qtwayland5
gdb
gdbserver
I have attempted to follow their guide on getting QT to work for YOCTO(not Debian) and have not gotten it to work. QT is installed but their Debian build does not come with a full sdk. Nor do they detail all of the packages that need to be installed.
I have also tried following this guide, but it was written for an RPI and X11 not wayland/Weston so some of the steps seem wrong especially in all of the packages it wants you to install.
https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/
Is there a good guide on how to do this, I was thinking of trying to combine the two guides by using his lines to set up rsync and such but I still do not have a full SDK without the right qmake.
My host system is UBUNTU 16.04
This is my first attempt at making a Qt Application work on different systems.
I have opted for static linking method.I have already compiled the sources of Qt 5.5 and compiled my application with the static Qt. The executable is working fine on my computer.
My operating system is Ubuntu 15.04. But when I tried to run the same executable on Ubuntu 14.04 then I ran into trouble. The key details of the error message are given below.
libstdc++.so.6 cxxabi_1.3.8 not found
I did a standard Google search and realised it was because I had a newer version of it on my machine, the machine where I had created the executable. There were so many different approaches to handle this problem. One of the solutions I saw involved shipping your own copy of libstdc++.so with the executable. But when I tried to copy the .so file to a pen drive, there was a warning saying that the file system does not support such files.
My question is , what am I doing wrong ? Also if I wanted to make the executable target Ubuntu 10.04, what would be the correct procedure handling the backward compatibility issues. I know that one method would be to install the same OS on my machine and then create the executable , is there any other way?
libstd++ is backward compatible but not forward compatible, which means you can run a program with a newer version of libstdc++ than the one you compiled it with but not vice-versa. This is what you experienced.
One way to deal with this issue is using older OS versions as the build machine. When you for example use Ubuntu 14.04 LTS, you'll get this list of compatible target systems.
The build system you're using will probably limit available compilers. On Ubuntu 14.04 you get GCC 4.8, which is good for most C++11 and packages for clang 3.6 are available, which will give you full C++14 support.
Targeting Ubuntu 10.04 will be challenging if you do not want to use a stone age compiler.
The idea of shipping libstdc++ will not help you much because you'll run into the same problem with libc.
I downloaded spark 1.0.2 and run on Cygwin
sbt/sbt assembly
but I got the error message:
Attempting to fetch sbt
You do not have curl or wget installed, please install sbt manually from http://www.scala-sbt.org/
But I already downloaded & installed sbt-0.13.5.msi from the given download-page. So what am I doing wrong?
sbt must use wget or curl to download additional dependencies, so you need to install these. On every single operating system other than windows these utilities usually come pre installed. Trying to get these to work on windows cygwin will be a pain, as with absalutely everything that isnt something to do with a monolithic GUI that costs a fortune.
I suggest if you wish to be at all productive in your future life you pick an operating system that works well for serious work. Windows only really works well for C# and MS office, serious computing? Big data? Hahahahaha, No!
i have a folder with an old plone version 2.5 and i would restore it on mac os mavericks or ubuntu 12.04. I know, that this really old plone version need python 2.4. I get it form python.org for mac os x but i don't found anything for ubuntu 12.04. I tried to restore this dump but it's not easy without a good documentation for version 2.5.
How can i restore this dump?
Start with an installer from https://launchpad.net/plone/2.5/2.5.5 . That will take care of not only Python, but also handle other binary components.
Install Plone on the target server, then transfer any custom add-on Plone products from the source server. Test it.
When that's running, copy the Data.fs file from the source to overwrite the Data.fs on the target.
I'm trying to install Qt-4.6.0-wince on XP and Vista. I read the instructions and follow it to install.
However, I can't install it successfully due to some fatal errors on all of the two machines. I think the problem is that qconfig.[h cpp] files are not created automatically during the configuration.
I already report about this problem, so you can see the more information here. However, it is still remained as unresolved.
Anybody here who has been installed it successfully?
#KernelJ I believe the original poster is using the correct install distro - the final product will be cross compiled from Win32 to WinCE; as is pointed out in the Qt for Windows CE Requirements.
#Brian, Unfortunately, I can't answer your original question - I have had unrelated trouble with the WinCE distribution myself and am working the issues now. However, I can provide some help: I was able to get the Qt Everywhere 4.6 to cross compile on my Win32 (XP) host for WinCE. I used the commercial version, but here is a link to the Open Source Qt Everywhere 4.6 package. As is pointed out in the nokia instructions, make sure to use the Visual Studio command prompt, get your environment variables ironed out, create a custom mkspec (if you have to), and keep a close eye during the configuration for any warnings.
Good luck.
Qt-4.6.0-wince, as is implied in the name and said explictly on the page you linked, is for Windows CE, NOT for Windows XP and Vista!!!
Nokia have released a nice software development kit for Qt which you can download here. It is very impressive and powerful!
I got things running as compilable (and running on emulator) with VS 2008, so your milage may vary:
Make sure the PATH variable points to \bin
Open a command prompt (using the Visual Studio Command Prompt)
Run the vcvars32.bat file (in C:\Program Files\Microsoft Visual Studio 9\VC\bin) folder
Cd into the qt folder
Run this: configure -no-sql-sqlite -no-qt3support -platform win32-msvc2008 –xplatform wincewm50pocket-msvc2008 -no-phonon -no-phonon-backend -no-webkit (building for WINCE 5.0, and all the '-no-...' makes it build faster, removing stuff we don’t want)
The setccepaths script provided sometimes doesn’t work. I used checksdk.exe –script temp_script.bat (It creates a script, the default is for Pocket PC SDK 5)
Run that script you just created (the temp_script.bat thing. It sets up environment variables.
Run nmake
*whew*
and good luck.