Content-Type: text/plain; charset=ISO-8859-1
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
2012/12/13 hermann meyer
> Am 13.12.2012 08:16, schrieb hermann meyer:
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
Content-Type: text/html; charset=ISO-8859-1
now it built, but no sound coming out...I opened using =
jalv.gtk and got the interface ok.is there a poss=
ibility it built wrong, but with a sucess exit status?
one more thingby what you've s=
aid, this LV2-amp comprises a 12ax7 tube amp + sovtek tonestak + 4x12 cabin=
et.would it be possible to have a plugins with al=
l the guitarix options of tubes, tonestaks and cabinets?
Thank you so muchGian=A0=A0
2012/12/13 hermann meyer <brummer-=
Am 13.12.2012 08:16, schrieb hermann meyer:<=
Am 13.12.2012 07:35, schrieb David Robillard:
On Thu, 2012-12-13 at 07:08 +0100, hermann meyer wrote:
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<email@example.com> =A0 wrote:
Looks like you are building against a static library. Since you are buildin=
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. =A0It is =
more of a
If you're building them yourself, ensure they're PIC, and it will w=
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
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. =A0Hence the "recompile with -fPIC&quo=
message from the linker :)
Thanks for confirm it.
I just wonder if there will be problems as well, when linking the executabl=
e (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=
if it's from another package. =A0If it is, on Lignux at least, plugins<=
depending on shared libraries isn't really a big deal anyway.
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 i=
s 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 loadi=
ng it, even if it increase the plug-so.size
So I will add the flag, and anyone could decide self what build method is p=
Linux-audio-dev mailing list
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO AM=