24 Jun
2011
24 Jun
'11
7:21 p.m.
I installed lv2core a couple of months ago on a Slackware 13.1 system,
and I created my own SlackBuild script to compile and install it, which
configured waf with "--prefix=/usr --configdir=/etc --libdir=/usr/lib64
--mandir=/usr/man". This put a copy of lv2.h in /usr/include/, and
another copy in /usr/lib64/lv2/lv2core.lv2/. I also installed SLV2
with no problems.
Since lilv came out (along with a couple of other packages to replace
SLV2), I decided to install it. I installed serd and sord first, but
when I try to compile lilv, it bombs out because it can't find
lv2/lv2plug.in/ns/lv2core/lv2.h (presumably, this path would be appended
to /usr/include/ for the complete path), and I can't figure out any way
to get lv2.h there without just creating each directory in the path
myself and copying it there. There is no mention of that path anywhere
in the waf scripts. The only mention I can find of that path is in the
README and INSTALL files, both of which suggest that programmers use that
path in their build scripts to determine whether lv2core is installed.
Why is that being recommended when the lv2core scripts don't install it
there? Am I missing something? This is driving me crazy. Any help
in preserving my sanity would be greatly appreciated.
Chuck
P.S. I've already tried putting this in my SlackBuild script:
sed -i -e "s,lv2/lv2plug.in/ns/lv2core/,," wscript lilv/lilv.h
and that allows it to compile and install alright, but it means I'll
also have to do something similar to every other program that looks
for lv2.h in that location, and that doesn't seem to be a be a very
nice solution.
24 Jun
24 Jun
7:28 p.m.
Hi Chuck,
I've only recently started using LV2, and decided to document exactly what I
done to get it all running.
Here's the link to the whole article:
http://harryhaaren.blogspot.com/2011/05/lv2-new-host-lib-lilv-newbies-guid-…
Here's the except you want:
If you get the following errors:
Checking for header lv2/lv2plug.in/ns/lv2core/lv2.h : no
Checking for header lv2/lv2plug.in/ns/ext/event/event.h : no
Checking for header lv2/lv2plug.in/ns/ext/event/event-helpers.h : no
Checking for header lv2/lv2plug.in/ns/ext/uri-map/uri-map.h : no
Then this is what you do:
1. Direct your browser to http://lv2plug.in/spec/
2. Grab lv2core
<http://lv2plug.in/spec/lv2core-4.0.tar.bz2>,lv2-event<http://lv2plug.in/spec/lv2-event-1.0.tar.gz>,
and lv2-uri-map <http://lv2plug.in/spec/lv2-uri-map-1.0.tar.gz>.
3. Untar lv2core, ./waf configure, ./waf, ./waf install it (the first one
should be fixed now)
4. Bop open a terminal, cd /usr/include/lv2/lv2plug.in/ns/
5. sudo mkdir ext
6. Copy the event folder into ext, and copy the uri-map folder in too.
7. *CHECK THE DIRECTORY STRUCTURE!!!* the output of ./waf configure tells
you *exactly* where its looking for the files, *PUT THEM THERE*. Can't
stress this enough. Use your brain & figure out what's not where its meant
to be
./waf configure should print out yes yes yes yes yes yes to all dependencies
now, so
./waf build,
HTH! -Harry
8:03 p.m.
On Fri, Jun 24, 2011 at 06:28:54PM +0100, Harry Van Haaren harryhaaren(a)gmail.com wrote:
I've only recently started using LV2, and decided
to document exactly what I
done to get it all running.
Here's the link to the whole article:
http://harryhaaren.blogspot.com/2011/05/lv2-new-host-lib-lilv-newbies-guid-…
Yes, I found your web page when trying to solve that, but it didn't fix
the problem.
Then this is what you do:
1. Direct your browser to http://lv2plug.in/spec/
I already did that (that's where I got lv2core when I installed it a
couple of months ago.
2. Grab lv2core
<http://lv2plug.in/spec/lv2core-4.0.tar.bz2>,lv2-event<http://lv2plug.in/spec/lv2-event-1.0.tar.gz>,
and lv2-uri-map <http://lv2plug.in/spec/lv2-uri-map-1.0.tar.gz>.
I have all of those, although I've only installed the first one.
3. Untar lv2core, ./waf configure, ./waf, ./waf
install it (the first one
should be fixed now)
I did that two months ago. I still have it installed, so it didn't fix
it for me. In fact I had already done that before lilv came out, in
preparation for installing SLV2. lv2core didn't put lv2.h where lilv
wants to find it, and I can't find anything in the configuration to make
it put it there. I don't know why such a long path should be required,
anyway. Shouldn't it be sufficient to just put it in, and look for it
in, /usr/include/ (or /usr/local/include/), or at least no deeper than
/usr/include/lv2/ (or /usr/local/include/lv2/)?
4. Bop open a terminal, cd
/usr/include/lv2/lv2plug.in/ns/
5. sudo mkdir ext
6. Copy the event folder into ext, and copy the uri-map folder in too.
7. *CHECK THE DIRECTORY STRUCTURE!!!* the output of ./waf configure tells
you *exactly* where its looking for the files, *PUT THEM THERE*. Can't
stress this enough. Use your brain & figure out what's not where its meant
to be
I haven't done these, but I wasn't getting those other errors, either,
for some reason.
../waf configure should print out yes yes yes yes yes
yes to all dependencies
now, so
../waf build,
It doesn't. Hence my question. Thanks, anyway.
Chuck
9:45 p.m.
Perhaps try the following:
-Ensure if lv2core folder contains lv2.h: ls /usr/include/lv2/
lv2plug.in/ns/lv2core/
-run ./waf build, and post the error message here, it will probably say
[2/9] blah blah file stuff.
-Open that file that its complaining about, and check to see what #include
stuff its doing regarding lv2.
With some more info on what file its failing on I can check what's going
wrong on my machine here.
Cheers, -Harry
10:19 p.m.
On Fri, Jun 24, 2011 at 06:28:54PM +0100, Harry Van Haaren wrote:
Hi Chuck,
I've only recently started using LV2, and decided to document exactly what I
done to get it all running.
Here's the link to the whole article:
http://harryhaaren.blogspot.com/2011/05/lv2-new-host-lib-lilv-newbies-guid-…
Here's the except you want:
If you get the following errors:
Checking for header lv2/lv2plug.in/ns/lv2core/lv2.h : no
Checking for header lv2/lv2plug.in/ns/ext/event/event.h : no
Checking for header lv2/lv2plug.in/ns/ext/event/event-helpers.h : no
Checking for header lv2/lv2plug.in/ns/ext/uri-map/uri-map.h : no
Then this is what you do:
1. Direct your browser to http://lv2plug.in/spec/
2. Grab lv2core
<http://lv2plug.in/spec/lv2core-4.0.tar.bz2>,lv2-event<http://lv2plug.in/spec/lv2-event-1.0.tar.gz>,
and lv2-uri-map <http://lv2plug.in/spec/lv2-uri-map-1.0.tar.gz>.
3. Untar lv2core, ./waf configure, ./waf, ./waf install it (the first one
should be fixed now)
now run lv2config !!!
following steps are not necessary.
4. Bop open a terminal, cd
/usr/include/lv2/lv2plug.in/ns/
5. sudo mkdir ext
6. Copy the event folder into ext, and copy the uri-map folder in too.
7. *CHECK THE DIRECTORY STRUCTURE!!!* the output of ./waf configure tells
you *exactly* where its looking for the files, *PUT THEM THERE*. Can't
stress this enough. Use your brain & figure out what's not where its meant
to be
./waf configure should print out yes yes yes yes yes yes to all dependencies
now, so
./waf build,
HTH! -Harry
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
torben Hohn
11:32 p.m.
On Fri, Jun 24, 2011 at 10:19:15PM +0200, torbenh torbenh(a)gmx.de wrote:
Hmmm...Does lv2config then create the lv2/lv2plug.in/ns/lv2core/
directory and copy lv2.h into it? And since I'm creating a Slackware
package (a .tar.bz2 file that then untars the files into their final
destinations), would I need to run lv2config after untarring the
package (i.e., include it in a post-install script)? Is it run without
arguments, or are there arguments required?
There doesn't seem to be any documentation on what lv2config is or does.
The only thing I can find is this from the INSTALL file: "The utility
lv2config builds standard LV2 style include directory trees, and is
necessary for compiling LV2 code." That's rather vague, but I assumed
it was to be run when compiling an LV2 plugin, and would be part of the
build process for those plugins (and hopefully included in the automated
make, scons, waf, etc., build scripts). There's nothing in the INSTALL
file that says anything about running it as part of the lv2core install
process.
Chuck
3. Untar
lv2core, ./waf configure, ./waf, ./waf install it (the first one
should be fixed now)
now run lv2config !!!
25 Jun
25 Jun
4:15 a.m.
On Fri, Jun 24, 2011 at 05:32:39PM -0400, Chuck Martin v4o42wl02(a)sneakemail.com wrote:
On Fri, Jun 24, 2011 at 10:19:15PM +0200, torbenh
torbenh(a)gmx.de wrote:
Hmmm...Does lv2config then create the lv2/lv2plug.in/ns/lv2core/
directory and copy lv2.h into it? And since I'm creating a Slackware
package (a .tar.bz2 file that then untars the files into their final
destinations), would I need to run lv2config after untarring the
package (i.e., include it in a post-install script)? Is it run without
arguments, or are there arguments required?
After a little experimentation, it seems lv2config needs to be run during
the installation of the package, rather than during the creation of the
package. This seems like a very bad way of doing it. It means that
there are two directories and a symlink that are installed, but that
aren't in the list of files the package manager knows to be a part of
the package, so if the package is ever removed, those extra directories
and symlink are left behind.
I found a way around this, but it isn't pretty, because it involves
building the package twice. During the first build, I run lv2config,
which doesn't find the lv2.h header file where it expects to find it, so
it does nothing. I then install this version, but I don't run lv2config
after installing. I then build the package a second time, and this time
when I run lv2config, it finds the header file where it expects to find
it, so it creates usr/include/lv2plug.in and usr/include/lv2plug.in/ns
in the directory where I'm building the package (it does this because
I run lv2config as "lv2config $PKG/usr/include"), and also creates
usr/include/lv2plug.in/lv2core as a symlink to /usr/lib64/lv2/lv2core.lv2,
where lv2.h has already been installed from the first incomplete build.
This all becomes a part of the rebuilt package, so I can then either use
removepkg to remove the first version without the two extra directories
and the symlink, and then install the corrected version with installpkg,
or I can use upgradepkg to replace it in one step. This seems like a
very kludgey way to do it, but it's the only way to make sure that it
will remove cleanly if I ever decide to do so.
What's the purpose of creating the extra subdirectories and symlink,
anyway, if the header file has already been installed in both
/usr/include/ and /usr/lib64/lv2/lv2core.lv2/? And why is it installed
twice in the first place? Isn't once enough?
Chuck
3. Untar
lv2core, ./waf configure, ./waf, ./waf install it (the first one
should be fixed now)
now run lv2config !!!
6:59 a.m.
On Fri, Jun 24, 2011 at 10:15:33PM -0400, Chuck Martin v4o42wl02(a)sneakemail.com wrote:
after installing. I then build the package a second
time, and this time
when I run lv2config, it finds the header file where it expects to find
it, so it creates usr/include/lv2plug.in and usr/include/lv2plug.in/ns
in the directory where I'm building the package (it does this because
I run lv2config as "lv2config $PKG/usr/include"), and also creates
usr/include/lv2plug.in/lv2core as a symlink to /usr/lib64/lv2/lv2core.lv2,
where lv2.h has already been installed from the first incomplete build.
I just realized I still had it wrong. The lv2config step needed to create
three directories (not two) and a symlink. To get it to do this, I had
to use "lv2config $PKG/usr/include/lv2", which created /usr/include/lv2,
usr/include/lv2/lv2plug.in, and usr/include/lv2/lv2plug.in/ns in the
package directory, and usr/include/lv2/lv2plug.in/lv2core as a symlink
to /usr/lib64/lv2/lv2core.lv2, where lv2 was. I discovered this when
lilv still failed to build. Now I got it right, and lilv built and
installed successfully.
Chuck
2:28 p.m.
On Fri, Jun 24, 2011 at 9:19 PM, torbenh <torbenh(a)gmx.de> wrote:
now run lv2config !!!
following steps are not necessary.
Thanks Torben, I've updated me text to include that. For some reason it
worked without my doing...
I don't know why at all at all, but what difference :)
Cheers, -Harry
26 Jun
26 Jun
2:40 p.m.
On Sat, Jun 25, 2011 at 01:28:04PM +0100, Harry Van Haaren wrote:
On Fri, Jun 24, 2011 at 9:19 PM, torbenh
<torbenh(a)gmx.de> wrote:
at least you spotted, that this is not communicated clearly enough.
at some point during the make install of lv2 extensions, lv2config
should be run, but i think some bug is preventing that from happening.
now run lv2config !!!
following steps are not necessary.
Thanks Torben, I've updated me text to include that. For some reason it
worked without my doing...
I don't know why at all at all, but what difference :)
Cheers, -Harry
--
torben Hohn
4902
days inactive
4904
days old
linux-audio-user@lists.linuxaudio.org
9 comments
3 participants
participants (3)
-
Chuck Martin -
Harry Van Haaren -
torbenh