![]() Here we go, version 0.2 is out, with the following changes: A better goal would of course be something akin to Google's Picassa, but this will do for now.Īlso, you're absolutely right, I should file a bug report, but now that tried reproducing the error (Reaper crashing on scanning VSTs from Bootsy) it worked - without gdiplus.dll (newer Wine though), so I guess I can remove that option from the next version of LinReaper :) In fact I'd rather have this standalone, preferably downloadable from these pages somewhere, so Linux newcomers won't have to go and find out if they like PlayOnLinux, Wine-Doors or if they should purchase CrossOver Wine, but instead they can just get the one from the Reaper forums that's build for the purpose. Python for the GUI and bash scripts for the actual work.ĭanKegel, I'm not sure about PlayOnLinux, it seems like a bit of a mess to me, plus there's also Wine-Doors, which frankly looks a bit better, so I'm not sure which to support. Hey thanks for all the quick and friendly responses, be sure to let me know it did what it should, or if you ran into any problems.Īlex, yes I did it in python and bash scripts. Works with latest Wine again (no more problems with the path to "Program Files")ĭownloading the latest version of Reaper automatically works again To use, double click the downloaded file and select "Run" if asked - you might also need to make the file executable by right clicking it and selecting Properties then the Permissions tab and checking "Allow executing file as a program". ![]() If the Cockos team is up for it, it would be very easy for me to change this into an actual Linux installer for Reaper, but I believe I have to get a green light first to not get into legal trouble. If you are using Ubuntu/Kubuntu/Xubuntu, Mint or Debian, the following should install everything you need:sudo apt-get install python-glade2 p7zip-full LinReaper requires Wine, Python, PyGTK (most distributions have these) and likes to also have the full 7Zip. In many regards, LinReaper is like Google's Picassa Linux port. Intelligently links the Wine folders "Desktop", "My Documents", "My Music", "My Pictures" and "My Videos" to their Linux counterparts Includes a tool (LinReaper Options) for installing and managing your Windows VSTs, JS effects, using Reapers more esoteric options and for advanced configuration of Wine Minimally configures the Reaper preferences for better Linux operation Sets up a wrapper script around Reaper to transform Reaper's configuration files to follow Unix/Freedesktop guidelines and allow automatic multi-user configurations Sets up a wrapper script around Reaper enabling it to accept normal UNIX command-line options and paths reapeak files (with custom icons), so you can simply double click Reaper files Sets up a local installation of WineAsio (again does not mess with the rest of your system) Installs Reaper in a bottled Wine directory (does not mess with the rest of your system) It's a very dirty thing and does not produce any deb package that you want to redistribute, but for personal use it works out very well usually.I thought I'd contribute to the Reaper Linux crowd by making our favourite software a little easier to install, so I would like to present to you, LinReaper.Īutomatically downloads and installs the newest Reaper version available from the website, or installs from a previously downloaded Reaper installation exe. This program generates a quick-n-dirty deb package for you so you can install and uninstall custom compiled software without having it hurt your system. There is a program called 'checkinstall' that will run the 'make install' step on your software for you. In Debian-land /usr/local is not touched by package-installed software so it can get messy without affecting any your 'normal' software, usually. The default place to install software is in /usr/local/ so if you want to 'uninstall' it you just delete it from there. Of course compiling software when your using Ubuntu or whatever should be avoided if you already have a existing package, but occasionally you'll want software with no native package. Then you can find the *-dev package, which contains the headers nessicary to compile software against already-existing binaries on your system. ![]() If configure fails with a missing dependancy, something like: Otherwise read the README or INSTALL files in the source code tarball. # this is were it checks for system configs and dependancies Most of the time people are using GNU make and autoconfig stuff so the basic steps, after untaring the source code, is: Well designed software usually doesn't have more then it needs so it's usually easier to deal with. Some software has a _lot_ of dependancies, which makes things a PITA. The most troublesome thing is figuring out the dependancies for a package. Compiling software can be intimidating, but it's usually not realy that big of a deal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |