28.10.2014 23:08, Robert Jonsson wrote: > 2014-10-28 19:46 GMT+01:00 Andrew Deryabin <[email protected]>: >> 28.10.2014 22:26, Robert Jonsson пишет: >>> Sorry it was a false report! >>> I had a LV2_PATH set to nowhere. >>> I got a gui now :) >>> >>> /Robert >> >> Wow! Cool! > Works on the other computer now too. > I'm a bit too tired to do any real testing though. Maybe in a few hours ;) Ok! >> I've added fallback library names to lv2 gtk2 helper. Now the order in which >> libraries are searched is: >> const char *gtk2LibraryNames []= {"libgtk-x11-2.0.so", >> "libgtk-x11-2.0.so.0", NULL}; >> const char *gtk2mmLibraryNames [] = {"libgtkmm-2.4.so", "libgtkmm-2.4.so.1", >> NULL}; >> >> So, it can solve problem on distros where only versioned libraries are >> installed (ubuntu case, I think). > The reasoning for these pre-built libs are to allow building MusE > without adding the gtk dependencies, right? Or are there other > reasons? Yes, only that. No other reasons. > Linux has a tendency to be a bit dodgy when it comes to preserving lib > interfaces (I have found it to be this way atleast) so I'm just > curious as to the reasons and if it would be an alternative to build > these too? I don't like when it comes to such a way - it's like a proprietary interfaces, that have no sources and ability for modification. But it makes things work without installing any gtk*-dev stuff...
May be I should add a slient check to cmake - it gtk2-dev and gtkmm2-dev were found, then include a visible option to compile gtk2 helper from source? And include an entry to the FAQ page describing process of using gtk2 lv2 interfaces in MusE (with instructions on howto recompile this support from source). Regards, Andrew > Regards, > Robert ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
