I again forgot to include the mailing list as another recipient of my last mail. Here it is:
---------- Weitergeleitete Nachricht ---------- Betreff: Re: [Lmuse-developer] Fwd: Re: LV2 upgraded, features, plus fixes in new branch lv2_fixes Datum: Dienstag, 17. Mai 2016, 14:57:02 Von: Jens Radloff <[email protected]> An: Tim E. Real <[email protected]> Hi Tim, hi all, > That's correct. There is only /one/ resultant liblv2_support.a file, > containing of all the objects. Ah, okay, so everything is fine. > Therefore MusE should be working and should be able to load > Gtk LV2 plugins such as Calf. Right? Yes, I checked this yesterday with one Calf synth, and I could see its GUI, but still with an error in its display. I will update issue #506 soon. Regards, Jens Am Montag, 16. Mai 2016, 14:22:21 schrieben Sie: > On Monday, May 16, 2016 07:54:12 PM Jens Radloff wrote: > > Sorry, I forgot to include the mailing list as another recipient of my > > last > > email. Here it is: > > > > ---------- Weitergeleitete Nachricht ---------- > > > > Betreff: Re: [Lmuse-developer] LV2 upgraded, features, plus fixes in new > > branch lv2_fixes > > Datum: Montag, 16. Mai 2016, 19:52:13 > > Von: Jens Radloff <[email protected]> > > An: Tim E. Real <[email protected]> > > > > Hi Tim, > > > > > So what ends up happening? Does it stop building or does it run? > > > > The build process did not stop building, and yes, I can start MusE. > > > > > The library is currently built static .a only, not shared .so. > > > > Ah, I see. > > > > But this is in conflict with that cmake -i option which asks you if you in > > general want to build static or shared objects. That is why I assumed that > > the LV2 libraries are shared objects. > > That's true. > I will look at respecting that flag, since all other modules do respect it. > For now the library is built as static only, I simply left it that way > since that's how it was always built before. > > Regardless, it shouldn't affect any behaviour at the moment. > > > > The place where the finished static library should be found is: > > > > > > <top_level_folder>/muse3/build/muse/lv2Support/liblv2_support.a > > > > There is such a file in my source code directory (where the compiled files > > are located, too). > > > > > You should see five folders named lilv, sord etc. > > > > Yes, they are there. > > > > > In those folders are the individual built *.o objects which make up > > > > > > the final *.a file. > > > > But there is no other *.a file than the file liblv2_support.a in the > > source > > code directory (where the compiled files are located, too). This command, > > > > executed in the top level folder of the source code directory: > > find ./* -type f -iname "*.a" > > > > returns only one file: the liblv2_support.a file. There are no *.a files > > for lilv, serd, sord, sratom. > > That's correct. There is only /one/ resultant liblv2_support.a file, > containing of all the objects. > > Therefore MusE should be working and should be able to load > Gtk LV2 plugins such as Calf. Right? > > > ----- > * Please note: > > I have just found a bug where if you load an LV2 plugin into a > track's effect rack, then you cannot load any more LV2 synth > or effect tracks - MusE just hangs there. > > Seems this was present before these changes. Investigating... > > Tim. > > > > If not, is it possible for you to post the screen output of a fresh, > > > > > > clean cmake configure, so I can follow what happens? > > > > > > If not, can you please post these files (they should exist): > > > > > > .../muse3/build/muse/lv2Support/CMakeFiles/lv2_support.dir/link.txt > > > > > > and > > > > > > .../muse3/build/muse/lv2Support/CMakeFiles/lv2_support.dir/flags.cmake > > > > I will do that tomorrow, because it is TV time now :-D > > > > Regards, > > > > Jens > > > > Am Montag, 16. Mai 2016, 13:01:59 schrieben Sie: > > > On Monday, May 16, 2016 08:21:20 AM Jens Radloff wrote: > > > > Hi Tim, > > > > > > > > Thanks for your support. It is 10 years ago that I for the last time > > > > checked out a branch with a similar software (SVN), so I need some > > > > assistance. > > > > > > > > Now I have a MusE source code directory in my music workstation that > > > > must > > > > contain the content of the lv2_fixes branch because, when running > > > > "cmake > > > > -i" in that source code directory, I now get asked about the > > > > ENABLE_LV2_SUPPLIED option. > > > > > > > > But no matter if I set this option to "OFF" or to "ON" during the > > > > cmake > > > > process, the LV2 libraries are not built in the source code directory. > > > > Having built MusE, I searched for them in the root directory of the > > > > source > > > > code directory with a command like > > > > > > > > find ./* -type f -iname "lilv*.so" > > > > > > > > or > > > > > > > > find ./* -type f -iname "*.so" > > > > > > > > , but the search results do not show any LV2 libraries (lv2, lilv, > > > > serd, > > > > sord, sratom) in the source code directory. (I did not specify a > > > > directory > > > > outside the source code directory as the target directory for the > > > > libraries > > > > to be built) > > > > > > > > The system LV2 libraries in my system have lower version numbers than > > > > the > > > > LV2 libraries that are supposed to be built from the source code of > > > > the > > > > lv2_fixes branch. > > > > > > > > These are the version numbers of these libraries provided by the > > > > Ubuntu > > > > repositories, installed in my Ubuntu 14.04.4 system: > > > > > > > > lv2: 1.8.0 (?) > > > > lilv: 0.16 > > > > serd: 0.18 > > > > sord: 0.12 > > > > sratom: 0.4.4 > > > > > > > > These versions are older than the versions of the LV2 libraries that > > > > should > > > > be built within the lv2_fixes branch. > > > > > > > > So how can I compile the built-in LV2 libraries? > > > > > > > > Regards, > > > > > > > > Jens > > > > > > Hi Jens, thanks for testing. Let's try to see what's wrong... > > > > > > So what ends up happening? Does it stop building or does it run? > > > > > > The library is currently built static .a only, not shared .so. > > > The place where the finished static library should be found is: > > > > > > <top_level_folder>/muse3/build/muse/lv2Support/liblv2_support.a > > > > > > You should see five folders named lilv, sord etc. > > > In those folders are the individual built *.o objects which make up > > > > > > the final *.a file. > > > > > > See anything? If so it should be running and working. > > > > > > > > > If not, is it possible for you to post the screen output of a fresh, > > > > > > clean cmake configure, so I can follow what happens? > > > > > > If not, can you please post these files (they should exist): > > > > > > .../muse3/build/muse/lv2Support/CMakeFiles/lv2_support.dir/link.txt > > > > > > and > > > > > > .../muse3/build/muse/lv2Support/CMakeFiles/lv2_support.dir/flags.cmake > > > > > > That will give me some first steps to check. > > > > > > Meanwhile I'm almost done my other work so I'll try to check here > > > > > > on my 14.04 > > > > > > Thanks. > > > Tim. > > > > > > > Am Sonntag, 15. Mai 2016, 12:54:17 schrieb Tim E. Real: > > > > > On Sunday, May 15, 2016 05:21:49 PM you wrote: > > > > > > Hi Tim, > > > > > > > > > > > > I could test the new branch "lv2_fixes" because I have an Ubuntu > > > > > > Studio > > > > > > 14.04.4 installation. I guess the system lv2 libraries in my > > > > > > installation > > > > > > are older than the ones that are built into this branch. I did not > > > > > > check > > > > > > that yet. > > > > > > > > > > > > Is the following command the correct command to download the > > > > > > source > > > > > > code > > > > > > of > > > > > > the lv2_fixes branch? > > > > > > > > > > > > git clone https://github.com/muse-sequencer/lv2_fixes.git > > > > > > > > > > > > ? > > > > > > > > > > > > If yes, this commands asks to specify a username (at that point I > > > > > > aborted > > > > > > the git command) and presumably a password. > > > > > > > > > > > > How should I proceed now? I do not know the user credentials for > > > > > > this > > > > > > command. Would it be reasonable to remove the user credentials > > > > > > protection > > > > > > from the lv2_fixes branch if one wants to download the source code > > > > > > of > > > > > > this > > > > > > branch? > > > > > > > > > > > > Regards, > > > > > > > > > > > > Jens > > > > > > > > > > Yes, git can be a mind-warping thing to understand :-) > > > > > > > > > > > > > > > git clone https://github.com/muse-sequencer/muse.git muse3 > > > > > > > > > > The last part (muse3) is your choice, can be any name. > > > > > It creates a folder by that name and downloads everything to that > > > > > folder. > > > > > > > > > > Once downloaded, change (cd) to that folder, and execute: > > > > > git branch -a > > > > > > > > > > to see a list of all the available branches. > > > > > > > > > > So then, in this case, you would want to execute: > > > > > git checkout lv2_fixes > > > > > > > > > > to switch to the lv2_fixes branch. > > > > > > > > > > (I think. If that fails, it might be "git checkout > > > > > remotes/origin/lv2_fixes".) > > > > > > > > > > Now proceed with cmake configuration, build, and install. > > > > > > > > > > ----- > > > > > Later, you can always switch branches again to any branch with > > > > > > > > > > git checkout <branch> > > > > > > > > > > In fact, if you /already/ have downloaded muse git before, > > > > > > > > > > you can just switch branches in that tree without downloading > > > > > again. > > > > > > > > > > That is, you can download just once, and switch branches > > > > > > > > > > 'on the fly' at any time. > > > > > > > > > > I've always found that to be the most mind-blowing thing about git. > > > > > When you switch branches 'in-place' like that, folders and files > > > > > > > > > > will magically disappear or appear depending on the branch. > > > > > > > > > > That was quite shocking to me at first, that a program would > > > > > > > > > > make things appear and disappear before your eyes like that. > > > > > > > > > > HTH. > > > > > Tim. > > > > > > > > > > > Am Samstag, 14. Mai 2016, 15:23:08 schrieb Tim E. Real: > > > > > > > Hey list. > > > > > > > > > > > > > > For the impatient, or those with an afternoon to kill, you can > > > > > > > try > > > > > > > > > > > > > > the brand *new* lv2 built-in support versions, in branch > > > > > > > lv2_fixes, > > > > > > > even if you are on a distro that uses the older versions, such > > > > > > > as > > > > > > > 14.04 LTS or even 15.* or 16.* (?) > > > > > > > > > > > > > > I have yet to merge with master. > > > > > > > I'm adding some more stuff in a different area (the gtkHelper > > > > > > > folder) > > > > > > > > > > > > > > so if you can go ahead and try /these/ changes, please do. > > > > > > > > > > > > > > Upgraded our built-in LV2 support library versions to: > > > > > > > lv2-1.12.0 > > > > > > > lilv-0.22.0 > > > > > > > serd-0.22.0 > > > > > > > sord-0.14.0 > > > > > > > sratom-0.4.6 > > > > > > > > > > > > > > I have kept their original tree structures /intact/ with version > > > > > > > numbers, > > > > > > > > > > > > > > and kept the NEWS, AUTHORS, COPYING etc, while still removing > > > > > > > all other unnecessary files. > > > > > > > > > > > > > > Instructions on how to upgrade the tree are given in > > > > > > > lv2Support/ChangeLog. > > > > > > > > > > > > > > But wait ! There's more ! > > > > > > > > > > > > > > All of this built-in support may not matter to most users now > > > > > > > because... > > > > > > > > > > > > > > [Drum roll] > > > > > > > > > > > > > > I added the ability to choose *system* versions instead of > > > > > > > *builtin* > > > > > > > See the new cmake setting ENABLE_LV2_SUPPLIED :-) > > > > > > > The default is off. > > > > > > > > > > > > > > You are permitted to choose the system versions *only* if they > > > > > > > > > > > > > > are greater than or equal to our versions listed above. > > > > > > > > > > > > > > Otherwise it automatically falls back to our built-in versions. > > > > > > > No worries. > > > > > > > > > > > > > > This is because some stuff was deprecated - it required mods to > > > > > > > MusE > > > > > > > - > > > > > > > > > > > > > > and a lot was fixed in the new LV2 versions. > > > > > > > > > > > > > > So MusE's code must at least /match/, or better, what is in the > > > > > > > > > > > > > > linked support libraries. > > > > > > > > > > > > > > Should future *system* LV2 versions break something in MusE, > > > > > > > > > > > > > > you can manually fall back to the built-in versions. > > > > > > > > > > > > > > Before I merge to master, I need to test on 14.04 distro, no > > > > > > > time > > > > > > > ATM, > > > > > > > > > > > > > > so please go ahead and test if you can. > > > > > > > > > > > > > > It should automatically force the built-in version to be built, > > > > > > > > > > > > > > assuming you have those way-too-old lv2 packages installed :-) > > > > > > > > > > > > > > Fixed a compile warning stoppage if using jack-1. > > > > > > > (That very old JackTransportNetStarting "case 4:" statement > > > > > > > HACK.) > > > > > > > > > > > > > > Suppressed unwanted Jack terminal errors and info output. > > > > > > > Although, it doesn't seem to be suppressing them with jack-1. > > > > > > > > > > > > > > Tim. ------------------------------------------------------------- ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
