Menu
▾
▴
linuxsampler-devel
|
From: Andrew C <cou...@gm...> - 2019-05-30 13:13:38
|
Hi all, It's me again! Just wanted to know what version of GTKMM is required for compiling gigedit? I'm planning on doing a Linuxsampler build on Void Linux (will be using this as my "workhorse" distro) this weekend, hopefully it'll be relatively painless. The Void Linux repos have gtkmm 3.x and 2.x available. Andrew. |
|
From: Christian S. <sch...@li...> - 2019-05-30 13:49:23
|
On Donnerstag, 30. Mai 2019 14:13:18 CEST Andrew C wrote: > Hi all, Hi Andrew. > It's me again! > Just wanted to know what version of GTKMM is required for compiling gigedit? > > I'm planning on doing a Linuxsampler build on Void Linux (will be using > this as my "workhorse" distro) this weekend, hopefully it'll be relatively > painless. > The Void Linux repos have gtkmm 3.x and 2.x available. gigedit supports gtk(mm) 2.x and 3.x. So that's completely up to you which one to pick. There should not be any problem with one of these. Just don't use the gtk(mm) 4.x development branch. 4.x should compile with gigedit, but behaviour is broken and fundamental features are missing. Chances are that gtk(mm) 4.x will never be supported by gigedit due to features being removed without replacement in gtk(mm) 4.x. Please note gtk versions > 3.24 is not Gtk 3, but actually already the Gtk 4 development branch version. So take care about that when you pick a package. CU Christian |
|
From: Andrew C <cou...@gm...> - 2019-06-05 06:38:29
|
Hi Christian, Thanks for the quick response. I've started the compilation on Void from the latest svn versions, but I'm running into trouble already with the ./configure for libgig: checking whether the g++ linker (/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether byte ordering is bigendian... no ./configure: 15609: ./configure: Syntax error: word unexpected (expecting ")") Bash version is: bash --version GNU bash, version 5.0.7(1)-release (x86_64-unknown-linux-gnu) Thanks, Andrew. |
|
From: Christian S. <sch...@li...> - 2019-06-05 09:14:55
|
On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: > Thanks for the quick response. I've started the compilation on Void from > the latest svn versions, but I'm running into trouble already with the > ./configure for libgig: > > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking dynamic linker characteristics... (cached) GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether byte ordering is bigendian... no > ./configure: 15609: ./configure: Syntax error: word unexpected (expecting > ")") Try to regenerate the configure script: make -f Makefile.svn ./configure make Were these tarball sources with pregenerated configure script? CU Christian |
|
From: Andrew C <cou...@gm...> - 2019-06-05 09:26:48
|
Hi Christian, No, these were the latest SVN sources with a re-generated configure script from make -f Makefile.svn Thanks, Andrew. On Wed, Jun 5, 2019 at 10:14 AM Christian Schoenebeck < sch...@li...> wrote: > On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: > > Thanks for the quick response. I've started the compilation on Void from > > the latest svn versions, but I'm running into trouble already with the > > ./configure for libgig: > > > > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports shared > > libraries... yes > > checking dynamic linker characteristics... (cached) GNU/Linux ld.so > > checking how to hardcode library paths into programs... immediate > > checking whether byte ordering is bigendian... no > > ./configure: 15609: ./configure: Syntax error: word unexpected (expecting > > ")") > > Try to regenerate the configure script: > > make -f Makefile.svn > ./configure > make > > Were these tarball sources with pregenerated configure script? > > CU > Christian > |
|
From: Andrew C <cou...@gm...> - 2019-06-06 18:11:20
|
Hi Christian, I think the latest commit to libgig fixed it (though I didn't see a changelog on the website). So I have successfully compiled and installed libgig. Now, onto Linuxsampler. First issue, can't find libgig. A misconfiguration on my end? Had to do "export PKG_CONFIG_PATH=/usr/local/lib/pkg-config:$PKG_CONFIG_PATH" and configure ran fine. Second issue, cannot find parser.h. Easy.. I just did a "make parser". Third roadblock: "g++ error: lscp_shell_reference.cpp: No such file or directory. g++: fatal error: no input files". Needed to install perl-XML-parser. Configuration and compilation of gigedit went without a hitch (just needed to install intltool and gtkmm 2.24). I'll admit, these issues were more due to my system than the code. Hopefully someone will find this info useful at some point in the future. Last issue I've got that I'll need to look at over the weekend is when I try and run gigedit: "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+3 in the same process is not supported." Thanks, Andrew. On Wed, Jun 5, 2019 at 11:26 AM Andrew C <cou...@gm...> wrote: > Hi Christian, > > No, these were the latest SVN sources with a re-generated configure script > from make -f Makefile.svn > > Thanks, > > Andrew. > > On Wed, Jun 5, 2019 at 10:14 AM Christian Schoenebeck < > sch...@li...> wrote: > >> On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: >> > Thanks for the quick response. I've started the compilation on Void from >> > the latest svn versions, but I'm running into trouble already with the >> > ./configure for libgig: >> > >> > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports shared >> > libraries... yes >> > checking dynamic linker characteristics... (cached) GNU/Linux ld.so >> > checking how to hardcode library paths into programs... immediate >> > checking whether byte ordering is bigendian... no >> > ./configure: 15609: ./configure: Syntax error: word unexpected >> (expecting >> > ")") >> >> Try to regenerate the configure script: >> >> make -f Makefile.svn >> ./configure >> make >> >> Were these tarball sources with pregenerated configure script? >> >> CU >> Christian >> > |
|
From: Andrew C <cou...@gm...> - 2019-06-07 10:07:29
|
Last message in this thread. Got gigedit running after a little poking and prodding. I was wary of the GTK version and I had chosen the gtkmm 2.24 package, not the 3.24 package. Obviously this caused gigedit to try and load the gtkmm 2.24 library and gtk3, hence my issues. Uninstalled gtkmm2.24 and then install gtkmm3.24. I recompiled and finally I got gigedit running. Andrew. On Thu, Jun 6, 2019 at 7:11 PM Andrew C <cou...@gm...> wrote: > Hi Christian, > > I think the latest commit to libgig fixed it (though I didn't see a > changelog on the website). So I have successfully compiled and installed > libgig. > > Now, onto Linuxsampler. > First issue, can't find libgig. A misconfiguration on my end? Had to do > "export PKG_CONFIG_PATH=/usr/local/lib/pkg-config:$PKG_CONFIG_PATH" and > configure ran fine. > Second issue, cannot find parser.h. Easy.. I just did a "make parser". > Third roadblock: "g++ error: lscp_shell_reference.cpp: No such file or > directory. g++: fatal error: no input files". Needed to install > perl-XML-parser. > > Configuration and compilation of gigedit went without a hitch (just needed > to install intltool and gtkmm 2.24). > > I'll admit, these issues were more due to my system than the code. > Hopefully someone will find this info useful at some point in the future. > > Last issue I've got that I'll need to look at over the weekend is when I > try and run gigedit: "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+3 > in the same process is not supported." > > Thanks, > > Andrew. > > On Wed, Jun 5, 2019 at 11:26 AM Andrew C <cou...@gm...> wrote: > >> Hi Christian, >> >> No, these were the latest SVN sources with a re-generated configure >> script from make -f Makefile.svn >> >> Thanks, >> >> Andrew. >> >> On Wed, Jun 5, 2019 at 10:14 AM Christian Schoenebeck < >> sch...@li...> wrote: >> >>> On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: >>> > Thanks for the quick response. I've started the compilation on Void >>> from >>> > the latest svn versions, but I'm running into trouble already with the >>> > ./configure for libgig: >>> > >>> > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports shared >>> > libraries... yes >>> > checking dynamic linker characteristics... (cached) GNU/Linux ld.so >>> > checking how to hardcode library paths into programs... immediate >>> > checking whether byte ordering is bigendian... no >>> > ./configure: 15609: ./configure: Syntax error: word unexpected >>> (expecting >>> > ")") >>> >>> Try to regenerate the configure script: >>> >>> make -f Makefile.svn >>> ./configure >>> make >>> >>> Were these tarball sources with pregenerated configure script? >>> >>> CU >>> Christian >>> >> |
|
From: Christian S. <sch...@li...> - 2019-06-07 19:03:37
|
You haven't mentioned which distro you are using. But usually you can avoid a huge bunch of hassle (which you obviously had) by just taking the packaging scripts for your specific distro instead of compiling and installing everything manually like you did. For instance if you compile packages for Debian with dpkg-buildpackage -b Then it already tells you which development packages you might need to install, it takes care about the correct library dependencies, the correct installation directories, approprirate configure script arguments and much more. Plus your installation would be much cleaner and easier to upgrade later on. CU Christian On Freitag, 7. Juni 2019 12:07:10 CEST Andrew C wrote: > Last message in this thread. > Got gigedit running after a little poking and prodding. > > I was wary of the GTK version and I had chosen the gtkmm 2.24 package, not > the 3.24 package. > Obviously this caused gigedit to try and load the gtkmm 2.24 library and > gtk3, hence my issues. > > Uninstalled gtkmm2.24 and then install gtkmm3.24. I recompiled and finally > I got gigedit running. > > Andrew. > > On Thu, Jun 6, 2019 at 7:11 PM Andrew C <cou...@gm...> wrote: > > Hi Christian, > > > > I think the latest commit to libgig fixed it (though I didn't see a > > changelog on the website). So I have successfully compiled and installed > > libgig. > > > > Now, onto Linuxsampler. > > First issue, can't find libgig. A misconfiguration on my end? Had to do > > "export PKG_CONFIG_PATH=/usr/local/lib/pkg-config:$PKG_CONFIG_PATH" and > > configure ran fine. > > Second issue, cannot find parser.h. Easy.. I just did a "make parser". > > Third roadblock: "g++ error: lscp_shell_reference.cpp: No such file or > > directory. g++: fatal error: no input files". Needed to install > > perl-XML-parser. > > > > Configuration and compilation of gigedit went without a hitch (just needed > > to install intltool and gtkmm 2.24). > > > > I'll admit, these issues were more due to my system than the code. > > Hopefully someone will find this info useful at some point in the future. > > > > Last issue I've got that I'll need to look at over the weekend is when I > > try and run gigedit: "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+3 > > in the same process is not supported." > > > > Thanks, > > > > Andrew. > > > > On Wed, Jun 5, 2019 at 11:26 AM Andrew C <cou...@gm...> wrote: > >> Hi Christian, > >> > >> No, these were the latest SVN sources with a re-generated configure > >> script from make -f Makefile.svn > >> > >> Thanks, > >> > >> Andrew. > >> > >> On Wed, Jun 5, 2019 at 10:14 AM Christian Schoenebeck < > >> > >> sch...@li...> wrote: > >>> On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: > >>> > Thanks for the quick response. I've started the compilation on Void > >>> > >>> from > >>> > >>> > the latest svn versions, but I'm running into trouble already with the > >>> > ./configure for libgig: > >>> > > >>> > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports > >>> > shared > >>> > libraries... yes > >>> > checking dynamic linker characteristics... (cached) GNU/Linux ld.so > >>> > checking how to hardcode library paths into programs... immediate > >>> > checking whether byte ordering is bigendian... no > >>> > ./configure: 15609: ./configure: Syntax error: word unexpected > >>> > >>> (expecting > >>> > >>> > ")") > >>> > >>> Try to regenerate the configure script: > >>> make -f Makefile.svn > >>> ./configure > >>> make > >>> > >>> Were these tarball sources with pregenerated configure script? > >>> > >>> CU > >>> Christian |
|
From: Andrew C <cou...@gm...> - 2019-06-07 19:26:59
|
Think I mentioned it up there, I'm running Void Linux and still getting to grips with it's package management + running from a minimal install environment (getting the dev environment set up and working was half the battle, as seen above). Thanks! Andrew. On Fri, Jun 7, 2019 at 8:03 PM Christian Schoenebeck < sch...@li...> wrote: > You haven't mentioned which distro you are using. But usually you can > avoid a > huge bunch of hassle (which you obviously had) by just taking the > packaging > scripts for your specific distro instead of compiling and installing > everything > manually like you did. > > For instance if you compile packages for Debian with > > dpkg-buildpackage -b > > Then it already tells you which development packages you might need to > install, it takes care about the correct library dependencies, the correct > installation directories, approprirate configure script arguments and much > more. Plus your installation would be much cleaner and easier to upgrade > later > on. > > CU > Christian > > On Freitag, 7. Juni 2019 12:07:10 CEST Andrew C wrote: > > Last message in this thread. > > Got gigedit running after a little poking and prodding. > > > > I was wary of the GTK version and I had chosen the gtkmm 2.24 package, > not > > the 3.24 package. > > Obviously this caused gigedit to try and load the gtkmm 2.24 library and > > gtk3, hence my issues. > > > > Uninstalled gtkmm2.24 and then install gtkmm3.24. I recompiled and > finally > > I got gigedit running. > > > > Andrew. > > > > On Thu, Jun 6, 2019 at 7:11 PM Andrew C <cou...@gm...> wrote: > > > Hi Christian, > > > > > > I think the latest commit to libgig fixed it (though I didn't see a > > > changelog on the website). So I have successfully compiled and > installed > > > libgig. > > > > > > Now, onto Linuxsampler. > > > First issue, can't find libgig. A misconfiguration on my end? Had to do > > > "export PKG_CONFIG_PATH=/usr/local/lib/pkg-config:$PKG_CONFIG_PATH" and > > > configure ran fine. > > > Second issue, cannot find parser.h. Easy.. I just did a "make parser". > > > Third roadblock: "g++ error: lscp_shell_reference.cpp: No such file or > > > directory. g++: fatal error: no input files". Needed to install > > > perl-XML-parser. > > > > > > Configuration and compilation of gigedit went without a hitch (just > needed > > > to install intltool and gtkmm 2.24). > > > > > > I'll admit, these issues were more due to my system than the code. > > > Hopefully someone will find this info useful at some point in the > future. > > > > > > Last issue I've got that I'll need to look at over the weekend is when > I > > > try and run gigedit: "GTK+ 2.x symbols detected. Using GTK+ 2.x and > GTK+3 > > > in the same process is not supported." > > > > > > Thanks, > > > > > > Andrew. > > > > > > On Wed, Jun 5, 2019 at 11:26 AM Andrew C <cou...@gm...> > wrote: > > >> Hi Christian, > > >> > > >> No, these were the latest SVN sources with a re-generated configure > > >> script from make -f Makefile.svn > > >> > > >> Thanks, > > >> > > >> Andrew. > > >> > > >> On Wed, Jun 5, 2019 at 10:14 AM Christian Schoenebeck < > > >> > > >> sch...@li...> wrote: > > >>> On Mittwoch, 5. Juni 2019 08:38:10 CEST Andrew C wrote: > > >>> > Thanks for the quick response. I've started the compilation on Void > > >>> > > >>> from > > >>> > > >>> > the latest svn versions, but I'm running into trouble already with > the > > >>> > ./configure for libgig: > > >>> > > > >>> > checking whether the g++ linker (/bin/ld -m elf_x86_64) supports > > >>> > shared > > >>> > libraries... yes > > >>> > checking dynamic linker characteristics... (cached) GNU/Linux ld.so > > >>> > checking how to hardcode library paths into programs... immediate > > >>> > checking whether byte ordering is bigendian... no > > >>> > ./configure: 15609: ./configure: Syntax error: word unexpected > > >>> > > >>> (expecting > > >>> > > >>> > ")") > > >>> > > >>> Try to regenerate the configure script: > > >>> make -f Makefile.svn > > >>> ./configure > > >>> make > > >>> > > >>> Were these tarball sources with pregenerated configure script? > > >>> > > >>> CU > > >>> Christian > > > |
Thanks for helping keep SourceForge clean.
X