11 Dec
2012
11 Dec
'12
5:38 p.m.
Looks like you are building against a static library. Since you are building a shared
module, pedantically you can't do this, in practice you at least need to be sure all
code is built with -fPIC. Presumably the static library mentioned is not, which is your
problem.
I am not familiar with libgxmm or the guitarix LV2 work specifically, sorry, no concrete
suggestions.
Gianfranco Ceccolini <franconassis(a)gmail.com> wrote:
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
11 Dec
11 Dec
7:29 p.m.
New subject: building the new Guitarix LV2 Amp
It isn't a problem to do that in a 32bit environment, but however, I
will set the build flag for libgxw/gxwmm to cshlib (build shared libs)
when the lv2 plug is set to build, to avoid such trouble.
As I said in the previous mail, just add --shared-lib to ./waf configure
will solved it for now.
greets
hermann
Am 11.12.2012 17:31, schrieb David Robillard:
Looks like you are building against a static library.
Since you are
building a shared module, pedantically you can't do this, in practice
you at least need to be sure all code is built with -fPIC. Presumably
the static library mentioned is not, which is your problem.
I am not familiar with libgxmm or the guitarix LV2 work specifically,
sorry, no concrete suggestions.
Gianfranco Ceccolini <franconassis(a)gmail.com> wrote:
Hello all
I've tried building the new LV2 Amp from guitarix and the following
error is ocurring
/usr/bin/ld: default/libgxwmm/gxwmm/libgxwmm.a(controlparameter_83.o):
relocation R_X86_64_32 against `_ZTTN3Gxw16ControlParameterE' can not
be used when making a shared object; recompile with -fPIC
default/libgxwmm/gxwmm/libgxwmm.a: could not read symbols: Bad value
I've already installed the last LV2 from SVN.
Using Debian Testing in my box.
Any ideas on waht I'm doing wrong?
Thanks for all
Gian
--
Antes de imprimir pense em sua responsabilidade e compromisso com o
MEIO AMBIENTE!
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
12 Dec
12 Dec
1:02 a.m.
New subject: building the new Guitarix LV2 Amp
On Tue, 2012-12-11 at 19:29 +0100, hermann meyer wrote:
It isn't a problem to do that in a 32bit
environment, but however
[...]
IIRC the rule is something like "works on most UNIX with the GNU
toolchain on 32-bit Intel architectures". But even then, only if it's
built as PIC.
You're better off just not doing it, and a 32-bit assumption stopped
being reasonable long ago anyway, it's been nearly a decade since
commodity 64-bit desktop hardware hit the market...
I only vaguely recall the above rule since I haven't had a 32-bit
userspace for about that long :)
Cheers,
-dr
12:26 p.m.
New subject: building the new Guitarix LV2 Amp
Am 11.12.2012 17:31, schrieb David Robillard:
I am not familiar with libgxmm or the guitarix LV2
work specifically,
sorry, no concrete suggestions.
well, libgxw is a additional gtk+2.0 widget library
with widgets mainly
for audio applications, libgxwmm is the gtkmm wrapper library for it.
Both are part of the guitarix source tree. Default use was as static
library for guitarix, i have change that now, so that it will be build
as shared library if the LV2 amp is selected to build.
The guitarix LV2 work is highly inspire by this tutorial from Harry Harren
http://harryhaaren.blogspot.de/2012/07/writing-lv2-guis-making-it-look-snaz…
and needs your latest LV2 specs 1.2.0
and this is how it looks now, thanks to Richard Dalton
http://www.Ampskindesigns.com
http://img827.imageshack.us/img827/6410/bildschirmfotovom201212.png
unfortunately a bug in the sourceforge GIT browser makes it nearly
impossible to browse the source online.
regards
hermann
8:35 p.m.
New subject: building the new Guitarix LV2 Amp
On Wed, 2012-12-12 at 12:26 +0100, hermann meyer wrote:
Am 11.12.2012 17:31, schrieb David Robillard:
Are you just depending on this lib being system installed, or including
it in the bundle?
I am not familiar with libgxmm or the guitarix
LV2 work specifically,
sorry, no concrete suggestions.
well, libgxw is a additional gtk+2.0 widget
library with widgets mainly
for audio applications, libgxwmm is the gtkmm wrapper library for it.
Both are part of the guitarix source tree. Default use was as static
library for guitarix, i have change that now, so that it will be build
as shared library if the LV2 amp is selected to build. The guitarix LV2 work is highly inspire by this
tutorial from Harry Harren
http://harryhaaren.blogspot.de/2012/07/writing-lv2-guis-making-it-look-snaz…
and needs your latest LV2 specs 1.2.0
and this is how it looks now, thanks to Richard Dalton
http://www.Ampskindesigns.com
http://img827.imageshack.us/img827/6410/bildschirmfotovom201212.png
Cool. I admit to having never tried Guitarix, but being able to get rid
of my POD will be nice :)
unfortunately a bug in the sourceforge GIT browser
makes it nearly
impossible to browse the source online.
No worries. I'll check it out (literally) some time over the holidays
-dr
9:17 p.m.
New subject: building the new Guitarix LV2 Amp
Am 12.12.2012 20:35, schrieb David Robillard:
The LV2 plug runs well in your jalv host, that's the
host I use for
developing.
Now, it also runs fine in qtractor-svn, after Rui have added support for
lv2 1.2.0 somewhat quick.:-)
Hope you enjoy it a bit :-)
regards
hermann
On Wed, 2012-12-12 at 12:26 +0100, hermann meyer
wrote:
No, don' t include in the bundle, they go to be system installed. (But
they don' t need to be installed during build, we use the use_liblocal
option for build time.)
Guitarix app need them as well (and install them) if they build-ed as
shared libs. Maybe it is time to break them out of guitarix and offer
them as separate lib-package?
(there is also the --lib-dev configure option to install the headers
and *.pc files as well, there is a python wrapper for it, and it comes
with Glade support)
just found a Reference page at sourcearchive:
http://guitarix.sourcearchive.com/documentation/0.20.2-2/dirs.html
it's from a older version, but there have not so much changed in the libs.
Am 11.12.2012 17:31, schrieb David Robillard:
Are you just depending on
this lib being system installed, or including
it in the bundle?
I am not familiar with libgxmm or the guitarix
LV2 work specifically,
sorry, no concrete suggestions.
well, libgxw is a additional gtk+2.0 widget
library with widgets mainly
for audio applications, libgxwmm is the gtkmm wrapper library for it.
Both are part of the guitarix source tree. Default use was as static
library for guitarix, i have change that now, so that it will be build
as shared library if the LV2 amp is selected to build. The guitarix
LV2 work is highly inspire by this tutorial from Harry Harren
http://harryhaaren.blogspot.de/2012/07/writing-lv2-guis-making-it-look-snaz…
and needs your latest LV2 specs 1.2.0
and this is how it looks now, thanks to Richard Dalton
http://www.Ampskindesigns.com
http://img827.imageshack.us/img827/6410/bildschirmfotovom201212.png
Cool. I admit
to having never tried Guitarix, but being able to get rid
of my POD will be nice :) unfortunately
a bug in the sourceforge GIT browser makes it nearly
impossible to browse the source online.
No worries. I'll check it out
(literally) some time over the holidays
-dr 
10:34 p.m.
New subject: building the new Guitarix LV2 Amp
On 11 December 2012 16:31, David Robillard <d(a)drobilla.net> wrote:
Looks like you are building against a static library.
Since you are building
a shared module, pedantically you can't do this
A static library is just a pile of object files. Of course you can
build a shared object against them. The problem is just that the
objects in this particular static library were built without PIC.
Chris
13 Dec
13 Dec
4:16 a.m.
New subject: building the new Guitarix LV2 Amp
On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam wrote:
On 11 December 2012 16:31, David Robillard
<d(a)drobilla.net> wrote:
Well, yes, "pedantically" was not quite the right word. It is more of a
sweeping generalization.
If you're building them yourself, ensure they're PIC, and it will work,
but it's reasonable to expect static libraries from elsewhere to be
non-PIC, particularly things that aim to be small since PIC code is
larger.
-dr
Looks like you are building against a static
library. Since you are building
a shared module, pedantically you can't do this
A static library is just a pile of object files. Of course you can
build a shared object against them. The problem is just that the
objects in this particular static library were built without PIC.
7:08 a.m.
New subject: building the new Guitarix LV2 Amp
Am 13.12.2012 04:15, schrieb David Robillard:
On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam
wrote:
So if I add -fPIC to the static lib build flags for libgxw/mm, it will
work on 64bit also?
Right now I prefer the static build, as long no other application or
plug use it.
hermann
On 11 December 2012 16:31, David
Robillard<d(a)drobilla.net> wrote:
Well, yes,
"pedantically" was not quite the right word. It is more of a
sweeping generalization.
If you're building them yourself, ensure they're PIC, and it will work,
but it's reasonable to expect static libraries from elsewhere to be
non-PIC, particularly things that aim to be small since PIC code is
larger.
-dr
Looks like you are building against a static
library. Since you are building
a shared module, pedantically you can't do this
A static library is just a
pile of object files. Of course you can
build a shared object against them. The problem is just that the
objects in this particular static library were built without PIC.
7:35 a.m.
New subject: building the new Guitarix LV2 Amp
On Thu, 2012-12-13 at 07:08 +0100, hermann meyer wrote:
Am 13.12.2012 04:15, schrieb David Robillard:
Yes, you should be able to link a shared library to a static library
compiled as PIC even on 64-bit. Hence the "recompile with -fPIC"
message from the linker :)
Probably fine if it's part of the same build process, maybe not so much
if it's from another package. If it is, on Lignux at least, plugins
depending on shared libraries isn't really a big deal anyway.
-dr
On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam
wrote:
So if I add -fPIC to the static lib build flags for libgxw/mm, it will
work on 64bit also?
Right now I prefer the static build, as long no other application or
plug use it. On 11 December 2012 16:31, David
Robillard<d(a)drobilla.net> wrote:
Well, yes,
"pedantically" was not quite the right word. It is more of a
sweeping generalization.
If you're building them yourself, ensure they're PIC, and it will work,
but it's reasonable to expect static libraries from elsewhere to be
non-PIC, particularly things that aim to be small since PIC code is
larger.
Looks like you are building against a static
library. Since you are building
a shared module, pedantically you can't do this
A static library is just a
pile of object files. Of course you can
build a shared object against them. The problem is just that the
objects in this particular static library were built without PIC.
8:16 a.m.
New subject: building the new Guitarix LV2 Amp
Am 13.12.2012 07:35, schrieb David Robillard:
On Thu, 2012-12-13 at 07:08 +0100, hermann meyer
wrote:
Thanks for confirm it.
Am 13.12.2012 04:15, schrieb David Robillard:
Yes, you should be able to link a shared library to a static library
compiled as PIC even on 64-bit. Hence the "recompile with -fPIC"
message from the linker :) On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam
wrote:
So if I add -fPIC to the static lib build flags for libgxw/mm, it will
work on 64bit also?
Right now I prefer the static build, as long no other application or
plug use it. On 11 December 2012 16:31, David
Robillard<d(a)drobilla.net> wrote:
> Looks like you are building against a static library. Since you are building
> a shared module, pedantically you can't do this
A static library is just a pile of object files. Of course you can
build a shared object against them. The problem is just that the
objects in this particular static library were built without PIC.
Well, yes,
"pedantically" was not quite the right word. It is more of a
sweeping generalization.
If you're building them yourself, ensure they're PIC, and it will work,
but it's reasonable to expect static libraries from elsewhere to be
non-PIC, particularly things that aim to be small since PIC code is
larger.
Probably fine if it's part of the same build
process, maybe not so much
if it's from another package. If it is, on Lignux at least, plugins
depending on shared libraries isn't really a big deal anyway.
-dr
Well, just if packagers like to split the package, which they often like
to do :-) , it will be handy to reduce the dependency. So that the LV2
plug is installable even if guitarix itself isn't installed.
As long libgxw/mm only lives in the guitarix package.
As well, the plug just use a small amount of the lib, so we can avoid
loading it, even if it increase the plug-so.size
So I will add the flag, and anyone could decide self what build method
is preferred.
regards
hermann
8:53 a.m.
New subject: building the new Guitarix LV2 Amp
Am 13.12.2012 08:16, schrieb hermann meyer:
Am 13.12.2012 07:35, schrieb David Robillard:
I just wonder if there will be problems as well, when linking the
executable (which is build without PIC) against a static lib with PIC
enabled?
On Thu, 2012-12-13 at 07:08 +0100, hermann meyer
wrote:
Thanks for confirm it.
Am 13.12.2012 04:15, schrieb David Robillard:
Yes, you should be able to link a shared library to a static library
compiled as PIC even on 64-bit. Hence the "recompile with -fPIC"
message from the linker :) On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam
wrote:
> On 11 December 2012 16:31, David Robillard<d(a)drobilla.net> wrote:
>> Looks like you are building against a static library. Since you
>> are building
>> a shared module, pedantically you can't do this
> A static library is just a pile of object files. Of course you can
> build a shared object against them. The problem is just that the
> objects in this particular static library were built without PIC.
Well, yes, "pedantically" was not quite the right word. It is more
of a
sweeping generalization.
If you're building them yourself, ensure they're PIC, and it will
work,
but it's reasonable to expect static libraries from elsewhere to be
non-PIC, particularly things that aim to be small since PIC code is
larger.
So if I add -fPIC to the static lib build flags for libgxw/mm, it will
work on 64bit also?
Right now I prefer the static build, as long no other application or
plug use it. Probably fine
if it's part of the same build process, maybe not so much
if it's from another package. If it is, on Lignux at least, plugins
depending on shared libraries isn't really a big deal anyway.
-dr
Well, just if packagers like to split the package, which they often
like to do :-) , it will be handy to reduce the dependency. So that
the LV2 plug is installable even if guitarix itself isn't installed.
As long libgxw/mm only lives in the guitarix package.
As well, the plug just use a small amount of the lib, so we can avoid
loading it, even if it increase the plug-so.size
So I will add the flag, and anyone could decide self what build method
is preferred.
regards
hermann
6:21 p.m.
New subject: building the new Guitarix LV2 Amp
now it built, but no sound coming out...
I opened using jalv.gtk and got the interface ok.
is there a possibility it built wrong, but with a sucess exit status?
one more thing
by what you've said, this LV2-amp comprises a 12ax7 tube amp + sovtek
tonestak + 4x12 cabinet.
would it be possible to have a plugins with all the guitarix options of
tubes, tonestaks and cabinets?
Thank you so much
Gian
2012/12/13 hermann meyer <brummer-(a)web.de>
Am 13.12.2012 08:16, schrieb hermann meyer:
Am 13.12.2012 07:35, schrieb David Robillard:
executable
(which is build without PIC) against a static lib with PIC
enabled?
Probably fine if it's part of the same build process, maybe not so much
______________________________**_________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.**linuxaudio.org<Linux-audio-dev@lists.linuxaudio.org>
http://lists.linuxaudio.org/**listinfo/linux-audio-dev<http://lists.linu…
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
On Thu, 2012-12-13 at 07:08 +0100, hermann meyer
wrote:
Thanks for confirm it.
I just wonder if there will be problems as well, when linking the Am 13.12.2012 04:15, schrieb David Robillard:
> On Wed, 2012-12-12 at 21:34 +0000, Chris Cannam wrote:
>
>> On 11 December 2012 16:31, David Robillard<d(a)drobilla.net> wrote:
>>
>>> Looks like you are building against a static library. Since you are
>>> building
>>> a shared module, pedantically you can't do this
>>>
>> A static library is just a pile of object files. Of course you can
>> build a shared object against them. The problem is just that the
>> objects in this particular static library were built without PIC.
>>
> Well, yes, "pedantically" was not quite the right word. It is more of
> a
> sweeping generalization.
>
> If you're building them yourself, ensure they're PIC, and it will work,
> but it's reasonable to expect static libraries from elsewhere to be
> non-PIC, particularly things that aim to be small since PIC code is
> larger.
>
> So if I add -fPIC to the static lib build flags for libgxw/mm, it will
work on 64bit also?
Right now I prefer the static build, as long no other application or
plug use it.
Yes, you should be able to link a shared library to a static library
compiled as PIC even on 64-bit. Hence the "recompile with -fPIC"
message from the linker :)
if
it's from another package. If it is, on Lignux at least, plugins
depending on shared libraries isn't really a big deal anyway.
-dr
Well, just if packagers like to split the package, which they often
like to do
:-) , it will be handy to reduce the dependency. So that the LV2
plug is installable even if guitarix itself isn't installed.
As long libgxw/mm only lives in the guitarix package.
As well, the plug just use a small amount of the lib, so we can avoid
loading it, even if it increase the plug-so.size
So I will add the flag, and anyone could decide self what build method is
preferred.
regards
hermann
7 p.m.
New subject: building the new Guitarix LV2 Amp
Am 13.12.2012 18:20, schrieb Gianfranco Ceccolini:
now it built, but no sound coming out...
I opened using jalv.gtk and got the interface ok.
is there a possibility it built wrong, but with a sucess exit status?
mm, I don't think so, if you start jalv it it a terminal you will get
some debugging output (from gxamp as well) if something goes wrong. If
all went well, gxamp wouldn’t output to the terminal.
Note that the default settings are lowered (-30db) so you need to turn
the gain up in order to receive sound. (right click on a controller
shows the values)
one more thing
by what you've said, this LV2-amp comprises a 12ax7 tube amp + sovtek
tonestak + 4x12 cabinet.
would it be possible to have a plugins with all the guitarix options
of tubes, tonestaks and cabinets?
Thank you so much
Gian
Maybe, but I play with the option to create several LV2 amp-heads out of
guitarix, instead put them all in one.
greets
hermann
7:08 p.m.
New subject: building the new Guitarix LV2 Amp
I´ve already tried turning all the knobs up with no luck.
about the LV2 plugins, would there be a performance difference between a
single plugin with the three engines (tube, tonestack and cabinet)
hardcoded in a single .so and separate plguins connected through JACK ?
regards
Gian
2012/12/13 hermann meyer <brummer-(a)web.de>
Am 13.12.2012 18:20, schrieb Gianfranco Ceccolini:
now it built, but no sound coming out...
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
I opened using jalv.gtk and got the interface ok.
is there a possibility it built wrong, but with a sucess exit status?
mm, I don't think so, if you start jalv it it a terminal you will get
some
debugging output (from gxamp as well) if something goes wrong. If all
went well, gxamp wouldn’t output to the terminal.
Note that the default settings are lowered (-30db) so you need to turn the
gain up in order to receive sound. (right click on a controller shows the
values)
one more thing
by what you've said, this LV2-amp comprises a 12ax7 tube amp + sovtek
tonestak + 4x12 cabinet.
would it be possible to have a plugins with all the guitarix options of
tubes, tonestaks and cabinets?
Thank you so much
Gian
Maybe, but I play with the option to create several LV2 amp-heads out of
guitarix, instead put them all in one.
greets
hermann
7:38 p.m.
New subject: building the new Guitarix LV2 Amp
Am 13.12.2012 19:07, schrieb Gianfranco Ceccolini:
I´ve already tried turning all the knobs up with no
luck.
And is there some output in the terminal?
about the LV2 plugins, would there be a performance difference between
a single plugin with the three engines (tube, tonestack and cabinet)
hardcoded in a single .so and separate plguins connected through JACK ?
No, non of relevance, at least, there is no difference in this or that.
regards
Gian
2012/12/13 hermann meyer <brummer-(a)web.de <mailto:brummer-@web.de>>
Am 13.12.2012 18:20, schrieb Gianfranco Ceccolini:
now it built, but no sound coming out...
I opened using jalv.gtk and got the interface ok.
is there a possibility it built wrong, but with a sucess exit
status?
mm, I don't think so, if you start jalv it it a terminal you will
get some debugging output (from gxamp as well) if something goes
wrong. If all went well, gxamp wouldn’t output to the terminal.
Note that the default settings are lowered (-30db) so you need to
turn the gain up in order to receive sound. (right click on a
controller shows the values)
one more thing
by what you've said, this LV2-amp comprises a 12ax7 tube amp +
sovtek tonestak + 4x12 cabinet.
would it be possible to have a plugins with all the guitarix
options of tubes, tonestaks and cabinets?
Thank you so much
Gian
Maybe, but I play with the option to create several LV2 amp-heads
out of guitarix, instead put them all in one.
greets
hermann
--
Antes de imprimir pense em sua responsabilidade e compromisso com o
MEIO AMBIENTE!
16 Dec
16 Dec
7:11 a.m.
New subject: building the new Guitarix LV2 Amp
On Thu, 2012-12-13 at 16:07 -0200, Gianfranco Ceccolini wrote:
I´ve already tried turning all the knobs up with no
luck.
about the LV2 plugins, would there be a performance difference between a
single plugin with the three engines (tube, tonestack and cabinet)
hardcoded in a single .so and separate plguins connected through JACK ?
If the signal path is linear and just normal mono or stereo audio needs
to be connected, most hosts could do this without having to do it via
Jack.
With so few plugins the overhead would be pretty low either way. In the
same host, too low to be of significance. Running plugins is just a
function call at the end of the day.
-dr
4157
days inactive
4162
days old
linux-audio-dev@lists.linuxaudio.org
16 comments
4 participants
participants (4)
-
Chris Cannam -
David Robillard -
Gianfranco Ceccolini -
hermann meyer