Re: [LAD] 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-snazzy.html 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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] 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: > > 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. Are you just depending on this lib being system installed, or including it in the bundle? > 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-snazzy.html > 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 signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] building the new Guitarix LV2 Amp
Am 12.12.2012 20:35, schrieb David Robillard: On Wed, 2012-12-12 at 12:26 +0100, hermann meyer wrote: 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. Are you just depending on this lib being system installed, or including it in the bundle? 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. 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-snazzy.html 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 :) 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.:-) 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 Hope you enjoy it a bit :-) regards hermann ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] building the new Guitarix LV2 Amp
On 11 December 2012 16:31, David Robillard 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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] building the new Guitarix LV2 Amp
On Wed, 2012-12-12 at 21:34 +, Chris Cannam wrote: > On 11 December 2012 16:31, David Robillard 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. -dr signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] building the new Guitarix LV2 Amp
Am 13.12.2012 04:15, schrieb David Robillard: On Wed, 2012-12-12 at 21:34 +, Chris Cannam wrote: On 11 December 2012 16:31, David Robillard 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. -dr 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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] 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: > > On Wed, 2012-12-12 at 21:34 +, Chris Cannam wrote: > >> On 11 December 2012 16:31, David Robillard 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 :) 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 signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] 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: Am 13.12.2012 04:15, schrieb David Robillard: On Wed, 2012-12-12 at 21:34 +, Chris Cannam wrote: On 11 December 2012 16:31, David Robillard 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 :) Thanks for confirm 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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] building the new Guitarix LV2 Amp
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 +, Chris Cannam wrote: On 11 December 2012 16:31, David Robillard 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 :) Thanks for confirm it. 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? 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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
