ardour

History

Robin Gareus 0f1b98c155 Linux installer: exclude backends from library compatibility test Engine backends are loaded dynamically, and Ardour can start without them. This is manly to relax the requirement of having libpulse.so. libardour itself depends on libasound, so the ALSA backend is always present, and the jack-backend dynamically dlopen()s libjack.		2020-04-09 15:47:11 +02:00
..
ardour.sh.in
build	Source-tree consistency (headless tools at top-level)	2020-03-26 19:00:41 +01:00
buildenv
install.sh
noderun
package
README
run
stage2.run.in	Linux installer: exclude backends from library compatibility test	2020-04-09 15:47:11 +02:00
uninstall.sh.in

README

* Installing Ardour:

On most distributions, you can double-click the file "install.sh".

Alternatively, you can use a Terminal to run the installer.  Navigate
to the folder and run:
	
	./install.sh
	
The installer will ask for your root password (sudo/su), and copy the 
contents of the appropriate bundle (32-bit or 64-bit) to your /opt
folder. 


* Links and Menu entries:

In addition to installing the program, the installer will create:
1) A desktop link to launch the Ardour application
2) A menu entry in Gnome/KDE
3) An uninstall script in the /opt folder.


* Uninstaller:

To uninstall Ardour, run the uninstaller script in the /opt folder.
This will remove the app, desktop links, menu links, and
the uninstaller itself.


* Manual Installation:

If you would prefer to install Ardour in a custom location, then you
may simply unzip the appropriate package (32bit or 64bit) to your
preferred location and run the Ardour application from the "bin"
folder inside.