[ardour-dev] Unpacking the tarball(s)

Taybin Rutkin taybin at earthlink.net
Fri Nov 3 07:03:11 PST 2006

.in files are generally files which are templates for other files to be created from.  So something like ardour.rc.in generates the ardour.rc file as part of the build.

.ac is autoconf.  .am is automake.  .po files hold the translations.  You can pretty much ignore the .ac and .am files, I hope.  They are leftovers from a previous build system.

-----Original Message-----
>From: John Emmas <johne53 at tiscali.co.uk>
>Sent: Nov 3, 2006 9:46 AM
>To: ardour-dev at lists.ardour.org
>Subject: Re: [ardour-dev] Unpacking the tarball(s)
>Thanks Paul,
>Manually changing the extensions to ".bz2" seems to have solved the problem.
>Most of the source files have the extension ".cc" - are they C++?  It looks
>like they are.  There are also some files with extensions I don't recognise,
>like ".in", ".ac", ".am" and ".po".  I guess I need to find the proper
>ardour-dev mailing list
>ardour-dev at lists.ardour.org

More information about the Ardour-Dev mailing list