-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temporary workaround for ZynAddSubFx name clashes #2118
Conversation
I feel It may be a good idea to merge this, as lmms appears to be lacking Devs that know about windows, meaning the zasf upgrade could be a long way off. An alternative could be to patch our zasf 2.4, although Im not sure that is any less of a hack |
8c45c1f
to
4da73f3
Compare
@tresf I saw you mention this PR over in #2269. I tried rebasing this today, and for whatever reason it worked when running it from
and the program exited with error code 127. I'm not sure what the issue is (I made |
@Wallacoloo I'm not an expert on the name clash stuff, but AFAIK, it was the remote processes that caused the hangup, so perhaps SDL uses something like that? I assume you've tried the obvious... changing |
76605e1
to
c1c9882
Compare
@tresf turns out that remnants of the old build were still sitting around even after running I pushed the results of the rebase to this branch, so it should merge fine if there's a concensus for this over @shimpe's #2494. |
Thanks. Merging to get |
@Wallacoloo one last thing... should we include a comment about why the name differs from the header? I feel someone may change this back later in a cleanup effort if we don't explain why the discrepancy occurs. |
665466c
to
c82d662
Compare
@tresf I added this blurb to the top & moved the typedef further up near that documentation:
|
Works for me on Arch. The console output is the same as @tresf's but lacks the shared memory error. |
…nflicts with ZASFx Document the Engine renaming better & link to relevant issues/PRs
c82d662
to
c519921
Compare
@tresf Squashed. I'm not getting the shared memory error either, but I am also using Arch. |
@Wallacoloo merging. Let's see how this goes. 👍 :) |
Temporary workaround for ZynAddSubFx name clashes
My entire desktop used to crash when clicking zyn's 'Show Gui'. Both in 1.1.3 branch and master (built from source). Today, Jan 5, I did a git clone https://github.com/LMMS/lmms.git No problems building lmms. When I run build/lmms and click zyn's Show Gui, my Desktop (Xserver?) still crashes. Running linux Mint 17.3 (xfce) :( |
@klopsi at the risk of stating the obvious, also make sure you don't have previous versions of lmms lingering about your system |
@shimpe the X-server crashing most likely isn't our bug. http://www.kvraudio.com/forum/viewtopic.php?f=47&t=440054&sid=331c5810b2f0c35f74814223e45ea91a |
@tresf Well.. it used to log me out of KDE before it was fixed. |
Thanks for your comments! The bug was in Xorg! Upgrading xorg using the ubuntu xorg-edgers ppa solved the problem. https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa |
Once Zyn 2.5 is ready to be merged, that should solve all the issues we've been having with the conflicting LMMS Engine and Zyn Engine classnames. Until then, this is the small patch that I've been using on my system in order to work around the issue (#2049, #2053, etc). It just renames Engine as LmmsCore, so that the two classes now have different symbol names, but then it typedefs it back to Engine so that the rest of LMMS doesn't need to be modified (for the most part).
I'm sharing this in case anyone else would find such a patch useful, and to see if there's demand for something like this to be merged while we work on readying Zyn 2.5. I must emphasize that this is meant to be temporary - I would not like to see this reside in the LMMS codebase for very long, if at all. Luckily, if people think this is worth merging, it's easy to revert once @curlymorphic's Zyn branch is merged.