23 Jul
2011
23 Jul
'11
4:59 p.m.
Just a quick question.
Is there a bug tracker for lv2 extensions?
Couldn't find it...
greetings,
lieven
23 Jul
23 Jul
5:23 p.m.
On 07/23/2011 09:59 AM, Lieven Moors wrote:
Just a quick question.
Is there a bug tracker for lv2 extensions?
Couldn't find it...
If it's a bug with the extension (which is usually just a
specification)... then it's up to the people who published the
extension. For the extensions published by lv2plug.in, I recommend
either the LV2 ML (http://lists.lv2plug.in) or the Trac site
(http://lv2plug.in/trac/)
However, if it's a bug with the implementation... that's /usually/ the
host application's bug (e.g. ardour or ingen or whatever).
-gabriel
5:53 p.m.
On Sat, Jul 23, 2011 at 10:23:13AM -0500, Gabriel Beddingfield wrote:
Thanks,
The trac site didn't seem like the place to file bugs.
Subscribing to a mailing list to submit one bug
doesn't seem right either.
Would be nice if the drobilla bug tracker could be used
for the extensions published by lv2plug.in.
lieven
6:16 p.m.
On Sat, Jul 23, 2011 at 05:53:43PM +0200, Lieven Moors wrote:
I guess the http://lv2plug.in/trac/ would be
the right place. But it looks like nobody has
ever used it, and there is only one ticket that
scared me off a little bit (something about a
casino).
lieven
8:54 p.m.
On Sat, Jul 23, 2011 at 11:16 AM, Lieven Moors <lievenmoors(a)gmail.com> wrote:
> The trac site didn't seem like the place to
file bugs.
[snip]
Simple: there are no bugs! Must be a problem on your end. :-P
But seriously... The lv2plug.in site was recently updated to being
trac-based in the last few months. And even so, bugs (or at least
bug REPORTS) have been rare because (a) most extensions are
set-in-stone specifications and (b) LV2 has been a little slow to
catch on.
-gabriel
8:19 p.m.
On Sat, 2011-07-23 at 17:53 +0200, Lieven Moors wrote:
[...]
The trac site didn't seem like the place to file
bugs.
If Trac doesn't seem like something to file bugs in, I don't know what
does...
Would be nice if the drobilla bug tracker could be
used
for the extensions published by lv2plug.in.
... Er, why? That's just another Trac site :P
-dr
9:10 p.m.
On Sat, Jul 23, 2011 at 02:19:39PM -0400, David Robillard wrote:
Oh, sorry, I was confused.
Via the drobilla site, there was a clear link
for reporting bugs. And I could file a bug without
log-in.
On the LV2 trac wiki there was no mention of bug
reports, and as the word ticket is not too familiar
for me (please don't laugh...), I didn't feel invited.
I still haven't found how to add a new
ticket on the LV2 trac. I think I have to have
a login first...
So the drobilla trac was fast and easy,
but LV2 trac was not.
I know, adding tickets without login, might not be
to safe. That's when you get 'casino' tickets :-)
On the other hand, I really hate it when you have
to get a log-in for every damn bug report...
(long live openid...)
But an extra link on the wiki might be nice.
And maybe an explanation if you have to get a
login first.
greetings,
lieven
9:21 p.m.
On Sat, 2011-07-23 at 21:10 +0200, Lieven Moors wrote:
On Sat, Jul 23, 2011 at 02:19:39PM -0400, David
Robillard wrote:
> On Sat, 2011-07-23 at 17:53 +0200, Lieven Moors wrote:
[...]
I know, adding tickets without login, might not be
to safe. That's when you get 'casino' tickets :-)
Indeed. No-login ticket filing is definitely completely out of the
question. You have to deal with ticket spam even when you have log-ins
*and* a captcha...
But an extra link on the wiki might be nice.
And maybe an explanation if you have to get a
login first.
Well, it's a wiki, so... ;)
That said, while the main page could probably use an overhaul anyway,
filing "bugs" against extensions isn't really a common thing for users
to want to do at all. They're specifications, not software...
-dr
9:22 p.m.
On Sat, Jul 23, 2011 at 09:10:42PM +0200, Lieven Moors wrote:
Since I'm not even sure it is a bug
in an LV2 extension, I might be forgiven
to post it here.
It's a problem you run into when you
try to configure one of the drobilla
packages (I think it's flowcanvas).
Configure fails, says that ext/event/event-helpers.h
cannot be found, even though it's there.
After scratching my head for a while,
I found out it's the waf test that is
failing.
On Harry Haaren's blog I found the
answer.
modify line 28 in event-helpers.h
by removing http from the address.
Hope it helps...
greetings
10:46 p.m.
On Sat, 2011-07-23 at 21:22 +0200, Lieven Moors wrote:
[...]
... Well, this thread was pretty silly. If it's a problem with building
my repository, hosted at drobilla.net, then yes, file bugs there :P
(Though it's certainly not flowcanvas, which has nothing whatsoever to
do with LV2)
Line 28 in event-helpers.h is an include line that does not contain
"http" anywhere:
http://lv2plug.in/repo/trunk/ext/event.lv2/event-helpers.h
The same is true of the version in the latest release of that extension:
http://lv2plug.in/spec/lv2-event-1.2.tar.bz2
<Insert lecture about complaining about bugs in old versions of things
here>
-dr
11:28 p.m.
I'm currently trying to update my system to the newer event spec, and I'm
having a hard time.
./waf configure
./waf
sudo ./waf install
works, but then the lilv wscript still won't see the event-helpers.h file.
I'm confused, and I think its due to not knowing what the file heirarchy of
the lv2 exensions is.
From what I gather:
Plugins should be installed here:
/usr/local/include/lv2/lv2plug.in/ns/ext/<name>/<name>.h
When ./waf install completes, you've still got to run lv2config.
What does lv2config do? I gather it symlinks the files around, or so? This
is what I can't figure out.
Help appreciated, -Harry
11:41 p.m.
On Sat, 2011-07-23 at 21:28 +0000, harryhaaren(a)gmail.com wrote:
Run lv2config.
No. Plugins are not extensions. They all live in bundles, though. All
bundles are typically in PREFIX/lib/lv2 or ~/.lv2
When ./waf install completes, you've still got to
run lv2config.
Indeed. Do it.
What does lv2config do? I gather it symlinks the files
around, or so?
This is what I can't figure out.
It builds the include directory tree so includes like:
#include "lv2/lv2plug.in/ns/ext/event/event.h"
work.
You don't really need a deep understanding of what is going on, only
that you must run lv2config after installing an extension to compile
against it.
-dr
5004
days inactive
5004
days old
linux-audio-dev@lists.linuxaudio.org
11 comments
4 participants
participants (4)
-
David Robillard -
Gabriel Beddingfield -
harryhaaren＠gmail.com -
Lieven Moors