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 <countfuzzb...@gmail.com> 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 <countfuzzb...@gmail.com> 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 < >> schoeneb...@linuxsampler.org> 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 >>> >>
_______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
