I built Ardour 5.12 the other day and came up with some inconsistencies, so I asked rgareus one of the devs for advice. He gave me the following:
1. sed -i 's/python ${SRC}/python2 ${SRC}/' libs/pbd/wscript is not needed this has been fixed in the source a long time. The only thing we have to do is to run python2 waf configure as the script already does.
2. configure it like this: configure --prefix=/usr --configdir=/etc --with-backends="jack,alsa,dummy" \ --libjack=weak \ --optimize \ --cxx11 \ --ptformat \ --no-phone-home
He said there is no need to build the documentation on the users machine. Add the dummy backend which improves on functionality. Optionally add the experimental --ptformat option which gives initial support for opening pro tools session in ardour. This is a work in progress but they have understood the XOR based encryption and are in the process of clean room reverse engineering the format.
On 2017-12-27 20:40:12 (+0100), Joakim Hernberg wrote:
I built Ardour 5.12 the other day and came up with some inconsistencies, so I asked rgareus one of the devs for advice. He gave me the following:
- sed -i 's/python ${SRC}/python2 ${SRC}/' libs/pbd/wscript is not
needed this has been fixed in the source a long time. The only thing we have to do is to run python2 waf configure as the script already does.
Nice.
- configure it like this: configure --prefix=/usr --configdir=/etc --with-backends="jack,alsa,dummy" \ --libjack=weak \ --optimize \ --cxx11 \ --ptformat \ --no-phone-home
He said there is no need to build the documentation on the users machine. Add the dummy backend which improves on functionality. Optionally add the experimental --ptformat option which gives initial support for opening pro tools session in ardour. This is a work in progress but they have understood the XOR based encryption and are in the process of clean room reverse engineering the format.
That's some neat improvement. However, I think building documentation can be quite benifical, as you might end up in a situation without internet connection, when working with ardour. I'd always opt for a local doc in that case. It should also be installed then.. ;-)
@Ray: Please add this to a new pkgrel!
Best, David
On 2017-12-27 20:40:12 (+0100), Joakim Hernberg wrote:
- sed -i 's/python ${SRC}/python2 ${SRC}/' libs/pbd/wscript is not
needed this has been fixed in the source a long time. The only thing we have to do is to run python2 waf configure as the script already does.
- configure it like this: configure --prefix=/usr --configdir=/etc --with-backends="jack,alsa,dummy" \ --libjack=weak \ --optimize \ --cxx11 \ --ptformat \ --no-phone-home
He said there is no need to build the documentation on the users machine. Add the dummy backend which improves on functionality. Optionally add the experimental --ptformat option which gives initial support for opening pro tools session in ardour. This is a work in progress but they have understood the XOR based encryption and are in the process of clean room reverse engineering the format.
I have updated the build script accordingly. A new version just hit [community-testing]. Apart from the features mentioned above, the PKGBUILD now also uses an auto-generated .desktop and mime .xml for XDG integration. The only downside is manually installing some hicolor-icon-theme pictures, but I'd rather do that than maintaining a separate .desktop file.
Thanks for the input, Joakim!
Best, David
arch-proaudio@lists.archlinux.org