-
-
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
Crash on open OS X "Lion" 10.7 (Apple) #1270
Comments
We currently don't build the software for OS X 10.7 "Lion" (we build for OS X 10.9 "Mavericks"). We will soon start building for OS X 10.10 "Yosemite". If you have a recommendation for making the build process backwards compatible with older OS X versions, please offer a recommendation to do so. If there's no easy way to make this backwards compatible we will close the bug as In the mean time, if you have XCode, you may want to try our MacPorts build tutorial and contribute this build yourself. We've made it pretty easy to follow: |
Apparently it's available using Cask for Homebrew, though that version seems to crash as well. |
@tres what is the minimum osx version we do support? On Tue, Dec 16, 2014 at 6:47 AM, Cameron [email protected] wrote:
Jonathan Aquilina |
Yeah, they are likely building with a newer version of XCode.
Well, we don't really know that for sure. We haven't tested it on an abundance of OSX versions. I need a bit of help in that regard. What we have today is a combination of what MacPorts had worked on and a lot of tweaking to our source code to compile with XCode (aka "Clang"). This was no small feat, but it will likely compile without much effort on other OSX versions. Most languages have a method for compiling with backwards compatibility to a certain OS level. I don't know how to to this but I'm willing to take recommendations. If we can get verification that the software only works on Mavericks and higher, I'd be happy to add that information to our "known issues" of our release notes. We could even go as far as labeling the download button, but our site is is very self-maintained in that regard and I'd be hesitant to hard-code something that is so volatile to change with each new OS X release... probably better for the release notes section (which we'll have starting with version 1.1). |
So it appears CMAKE supports this using the following flag: $ cmake .. -DCMAKE_INSTALL_PREFIX=../target/ -DCMAKE_OSX_DEPLOYMENT_TARGET=10.7 But it errors with:
So this appears to be completely possible with the right build environment, I'm just unsure the proper way to set this all up. My Mavericks VM has run out of disk space, so this will be a timely operation for me to setup (Apple doesn't allow the easy expansion of drives). If someone else (i.e. @eagles051387) has time to build against 10.7, please do. @soycamo I assume you're on 64-bit hardware, as I don't plan on making multi-arch builds for OSX. 😸 |
@tresf Yes! Most Macs that can run Snow Leopard (10.6) can use 64-bit binaries, with a few exceptions (I think the earliest MacBooks can't...) |
Ok, I'll try doing a symlink from a removable drive. I found XCode 4.6.3 which appears to be the latest available for Lion:
Once this is finished downloading and extracting, I'll attempt the Symlink SDK trick from the stackoverflow article: sudo ln -s /mnt/drive/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/ \
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/ |
So far there are two bugs with XCode 4.6.3 which are related to an ambiguous use of the So for now I've disabled the Mallets using Please test: (apologies for the versioning mismatch, I forgot to bump the version prior to build) For record... copy of stk/mallets error:
|
On 12/16/2014 09:50 PM, Tres Finocchiaro wrote:
Can you give me line numbers? |
Sure.... what's interesting is it didn't fall with Mavericks so Apple must have changed something... |
Ok should be fixed now. |
👍 |
I got a more interesting failure this time (from the executable in #1270 (comment))
|
Thanks for trying. Yeah, I think I need to build on Lion directly or do a full MacPorts update using the Lion compiler (something that takes several hours and would completely wipe out the Mavericks dependent libraries) To explain what's happening... Although LMMS was properly build against XCode 3.6.x, the QT libraries it uses are but against and they are still trying to talk to Mavericks. This is likely the same problem that we're seeing with STK/Mallets. |
I contacted the MacPorts team and to summarize our conversation, what we're trying to achieve with cross-compilation is not officially supported and also not recommended. ... So we have to setup a Lion machine. VirtualBox doesn't support Lion very well, so:
LMMS dependencies are downloading now. This will take the majority of the afternoon. I will post my progress here. |
@soycamo @coppolaemilio please try this version: https:/tresf/lmms/releases/download/v1.0.100/lmms-1.0.100-mac10.7.dmg @eagles051387 can you test this on Yosemite? We can target Lion for a while if it's forward compatible with newer OSs. |
Great, I'll close this out. I'd also like some testing on Mavericks and Yosemite @eagles051387. If we can get away with making a Lion build for all OSs that may be ideal. |
Oh and @eagles051387 since you only seem to read the last post in a bug report, here's the link to the Lion installer: https:/tresf/lmms/releases/download/v1.0.100/lmms-1.0.100-mac10.7.dmg |
I get this error every time I try to run it:
Edited 2014-11-17 @tresf for formatting
The text was updated successfully, but these errors were encountered: