I have a Raspberry Pi model B that I just bought. I downloaded and built the complete Mono source code to try to solve the hard float issue because supposedly a developer just committed a fix in the 3.2.7 version.
I have done the build and it worked without errors. I would now like to create a package or tarball or something that I can use to take what I just built and install it on other RPi devices.
Can someone tell me how to do this?
Related
I'm trying to add QtVirtualKeyboard to my standalone application. My app running without desktop but i don't think this is the problem. I found that we can integrate to my QMainWindow a QObject that show the keyboard along my app. I also found that it possible to use QQuickView and inputPanel, but sincerely, im not sure how to make it. Anyone can help?
To make it "works" i used this topic Install QtVirtualkeyboard in raspberry-pi? then i have installed QtVirtualKeyboard with this commandsudo apt install qtvirtualkeyboard-plugin. I said "work" because if i didn't install with apt, my application did nothing.
When installing mono on raspberry, using the official way described on mono website, i get a bunch of precompilation
example:
Mono precompiling /usr/lib/mono/4.5/mcs.exe for arm...
It takes lot of time, and i also got some raspberry rebooting during the task :(
is there a way to install mono without this precompilation stage ?
According to the person in charge of Mono packaging in Microsoft, this problem is fixed in the preview (not stable) channel which brings you Mono 5.18: https://www.mono-project.com/download/preview/.
I am currently working from Mono Version 3.2.8 and am running into trouble finding any documentation on this version. I have no idea what code will run until after I get the exceptions. Either a compatibility list to what works or an idea of what version I can compile that works would be great. Any one have experience with this?
You can manually install the latest version. I was easily able to install
Mono version 4.6.2 on Raspbian.
The http://www.mono-project.com/docs/ site gives a general answer for which major libraries work. Letting you know when there isn't full compatibility but doesn't give specifics.
To install QGIS on my MacBook Pro I need to install the gdal framework; however, the 1.11 framework package needed for QGIS is an empty file at kyngchaos. I tried installing GDAL 1.10 complete, but QGIS is requiring 1.11. I have Mavericks. I've installed each individual package: UnixImageIO, PROJ, GEOS, SQLite2, numpy, rgdal, and on... Now when I run the GDAL 1.11 framework install, everything seems to run until the last page, where an "Install Fail" page shows up. When I try to view the error, I'm taken out of the installer.
After some googling, I tried installing using homebrew. (brew install gdal)... I got a little further, but it tells me to "brew link libpng libtiff" -- and when I run that command, I get:
Linking /usr/local/Cellar/libpng/1.5.14... Warning: Could not link libpng. Unlinking...
Error: Could not symlink file: /usr/local/Cellar/libpng/1.5.14/share/man/man3/libpngpf.3
/usr/local/share/man/man3 is not writable. You should change its permissions.
After some more searching, it seems I could change permissions from usr/local to me, but I'm not sure how to (exactly) and don't want to mess anything up. Any help would be greatly appreciated, and my apologies if I'm missing something painfully obvious! I'm a novice at the programming end of things, so am just kind of pushing through everything like a bull in a china shop.
UPDATE:
Okay, I found the answer, even though it didn't seem to be working initially--
I ran the following commands from the GDAL help documentation:
export PATH=/Library/Frameworks/GDAL.framework/Programs:$PATH
sudo ln -sfh [ver] /Library/Frameworks/GDAL.framework/Versions/Current
in Terminal, and the framework was updated. If I run the GDAL 1.11 installer it still shows up as a failed installation, BUT QGIS recognizes 1.11 as the installed, so that's great.
(I just needed to install matplotlib in addition, and QGIS was installed successfully.)
It seems that the GDAL Complete framework was just updated 3 days ago, so it should be a temporary error until they realize the package is empty.
I have a Kinect for Windows and I would like to connect it to my Mac laptop with OSX 10.7.5.
I would like to use openNI as the driver.
OpenNI's website lists "OpenNI 2.1 Beta (OS X)" however the source-code page does not list install instructions. Are they found someplace else?
There are install instructions on the OpenNI 1.x github page and on OpenNI 1.x Unstable branch page. The instructions for the two branches are slightly different, however neither have worked for me.
I originally had XCode 4.6 installed. Both instructions state they want XCode 4.3.2, which I installed, renamed XCode 4.6 and used "sudo xcode-select -switch" to switch between them.
Both instructions ask for "libusb-devel +universal" and in both cases I get:
Error: Please do not install this port since it has been replaced by 'libusb'.
Error: org.macports.configure for port libusb-devel returned:
Please see the log file for port libusb-devel for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libusb-devel/libusb-devel/main.log
Error: Processing of port libusb-devel failed
If I continue with the installation of "libusb +universal" instead, then the rest of the dependencies install fine (though I had to install GraphViz before Doxygen).
But then when I run: "./RedistMaker" I get a lot of warnings, though it does create a Final file. "sudo ./install.sh" runs fine and I'm guessing OpenNI is installed, but then I get a bunch more errors when trying to install Sensor.
Can anyone help tell where along the way should I have started to worry? Do I need to manually install libusb (which I have tried to do)?
Any help appreciated!
I fixed the installation of OpenNI by running these instructions:
> sudo rm -f /opt/local/lib/libusb-1.0.0.dylib
> sudo port clean libusb
> sudo port install libusb +universal
Basically the Mac install instructions need to be updated and should include a warning that the short install may leave files around that will need to be deleted before installing with port.