[Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps

Heinz Wiesinger pprkut at liwjatan.at
Sat Mar 16 19:25:57 UTC 2013

On Saturday 16 March 2013 14:34:58 B Watson wrote:
> On 3/15/13, openpandora at free.fr <openpandora at free.fr> wrote:
> > cwiid needs to be patched to generate a .pc . I made one totally dirty
> > myself:
> The cwiid developers haven't done a release that includes a .pc file. If
> Ardour3 needs cwiid.pc, then it depends on an unstable (SVN) version
> of cwiid.
> I can update the cwiid package to build the same version as Debian/Ubuntu
> uses, which they call "0.6.00+svn201-2+b2". Presumably it works OK with
> Ardour or else the Ardour folks wouldn't be using it (AFAIK their primary
> development platform is Ubuntu).
> Out of curiosity, are you actually going to use a Wiimote to control
> Ardour, or are you just trying to build Ardour3 with all the optional
> deps enabled?

This is obviously a choice that's up to the cwiid maintainer, but IMHO there's 
no reason for us to /have to/ update the build to include the .pc file. If it 
doesn't work with what we currently have in the repo I would probably just 
drop the support for it from the ardour build.

> > New deps:
> > 
> > serd
> > sord
> > sratom
> > lilv
> This is going to open a can of worms. serd/sord/lilv are the new LV2
> stack, which replaces lv2core and slv2. Back when I first looked at these,
> I found that the old and new lv2 stacks couldn't easily coexist on the
> same system... and everything on SBo that uses LV2 currently depends on
> the old stack.

Ardour2 already needs those and they are already on SBo. If there is a conflict 
between slv2 and lilv I didn't see it and it needs to be dealt with.

> So we've got 2 options:
> 1. Figure out a way for lv2core/slv2 to coexist with lilv/serd/sord. This
> could be done by using different --libdir and such (the way fltk and
> fltk13 do), but AFAIK it will mean that your actual LV2 plugins will have
> to be built twice if you want them available for apps using either stack.

I don't see how that is the case. lilv still needs lv2. The plugins end up in 
the same place. Why would you have to build them twice?

> 2. Ditch the old stack. Every app on SBo that uses LV2 will have to be
> updated to use the new stack, assuming it even can use it (most can). I'd
> vote for this solution, but it'll require coordinated effort between
> many people, some of whom probably won't have the time/energy/desire to
> update their already-working builds.

calf, foo-yc20, swh-plugins-lv2, zynjacku are the only SlackBuilds in the repo 
depending on slv2. Nothing depends on lilv yet (Not counting optional 

> The absolute worst "solution" would be for someone to just blindly submit
> builds for serd/sord/lilv. We'd end up with mutually-incompatible sets
> of builds, and LV2 plugins that only work in certain apps, and maybe
> apps that crash (old-style LV2 stack, trying to load plugins built for
> the new).

Well, considering that should be the case since the 14.0 repo went live and I 
haven't seen a single mail about either on the ML or to me directly I doubt 
it's a big issue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130316/baf51d36/attachment.asc>

More information about the SlackBuilds-users mailing list