I've had trouble locating an actual step-by-step guide in which to get the "SphereEngine" running. I have my "frameworks" folder in the Library folder (which I believe I read I should do), but the engine still does not run. Honestly, I have no idea what I'm doing. Hahaha :) :o :'(
I haven't used Sphere since I had my good ol' Windows 98 maybe 10 years ago. Goodness.
Thanks!
Have you tried the sourceforge site (http://sourceforge.net/projects/sphere/)?
What I did was move all the frameworks into the Engine.app/Contents/Frameworks, but that failed. It started looking for a framework that wasn't in the package.
If you get it to work, please tell me :D
// Rahkiin
Have you tried the sourceforge site (http://sourceforge.net/projects/sphere/)?
Yep, that's where I downloaded it from. Whenever I try to open "SphereEngine" I get the error "SphereEngine cannot be opened because of a problem." I wasn't sure if that was because of the location of the "framework" folder or if it is some other issue. "Config" opens just fine.
You have now reached the end of my expertise :-\
Last time I tried it, on OS X 10.5, everything just worked. I didn't even need the frameworks archive.
Haha, it's all good. Thanks anyway!
BTW, you need to put the .frameworks located in the framework folder, in the ~/Users/<name>/Library/Frameworks/ folder. So without the framework folder itself. (I think the User Library works too, else try /Library/Frameworks). I am not sure from your story whether you copied the folder too or not :)
BTW, you need to put the .frameworks located in the framework folder, in the ~/Users/<name>/Library/Frameworks/ folder. So without the framework folder itself. (I think the User Library works too, else try /Library/Frameworks). I am not sure from your story whether you copied the folder too or not :)
Cool, good to know. Definitely didn't do it that way. SphereEngine still fails to open so I assume my issue is something else entirely. Thanks!
What error does it give, exactly?
I'm now keeping track of this topic. Next time I'm on my MacBook I'll give it a go and see if I can resolve this issue. I'm almost certain it's a misplaced directories (the frameworks) issue since this sounds really familiar to me, but without being in front of the thing I can't confirm it.
What error does it give, exactly?
The exact error is:
"SphereEngine cannot be opened because of a problem. Check with the developer to make sure SphereEngine works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X."
It's pretty vague so I'm not exactly sure how to proceed. The Sphere folder is on the Desktop at the moment, with the frameworks files in the Frameworks folder in the user library.
I'm now keeping track of this topic. Next time I'm on my MacBook I'll give it a go and see if I can resolve this issue. I'm almost certain it's a misplaced directories (the frameworks) issue since this sounds really familiar to me, but without being in front of the thing I can't confirm it.
Thanks! I appreciate it.
What version of OS X are you using? We know it's got serious issues with Mavericks.
Check with the developer to make sure SphereEngine works with this version of Mac OS X
...
What version of OS X are you using? We know it's got serious issues with Mavericks.
Lion -> 10.7.5
I can only personally guarantee Leopard and 32-bit Snow Leopard compatibility since my MacBook Pro is too old (early 2006 Intel Core Duo MacBook Pro 17") to install 10.7 or newer. I would pleasantly surprised if if works in any capacity in Lion, especially in 64-bit since the thing was a Universal Binary for PPC+x86 rather than x86+x64.
I can only personally guarantee Leopard and 32-bit Snow Leopard compatibility since my MacBook Pro is too old (early 2006 Intel Core Duo MacBook Pro 17") to install 10.7 or newer. I would pleasantly surprised if if works in any capacity in Lion, especially in 64-bit since the thing was a Universal Binary for PPC+x86 rather than x86+x64.
A bit off-topic, but x86+x64 strikes me as a colossal waste of space seeing as any x64 CPU can run x86 code just fine. Unless the situation is different on OS X than on Windows/Linux? I've never used any Mac OS past OS 9 way back in high school, so my knowledge in that area is admittedly slim...
OS X used to be primarily for PowerPC. Of no relation to x86 at all. So you really did need universal (aka 'fat') binaries for a while.
And remember that running x86 binaries on x86_64 requires all the necessary libraries exist in 32-bit form on the machine. This might not be the case here, particularly given how long ago Sphere was ported to OS X.
The OSX platform is almost only updated for the 64 bit software. It means that any new programs will be compiled to 64 bit, and that the new libraries only exist in 64bit. The fragile Objective-C ABI is also 64 bit only, and a lot of optimizations is 64bit only. When writing for OSX, it is mostly 64bit only nowadays.
Ah, alright, that makes sense then. And yes, I knew OS X used to be for PPC, I had nothing against PPC+x86 fat binaries, it's just the x86+x64 ones that seemed like a waste of space. But if most of the low-level libraries for OS X are 64-bit-only, then it makes sense. I guess I'm just biased because I've been spoiled from using Windows for so long, which has always included the full set of Win32 libraries along with the Win64 ones, and thus x86-only apps run natively. And I'm not positive, but I think Linux might be the same as Windows in that regard.
X86 applications run natively, but they can't use some new stuff. Chrome used to run in 32 bit, IIRC. AFAIK, I don't see any 32 bit programs running on my system now. There is just no reason to run in 32 bit :P
On windows and linux, there are reasons to do so. Mostly way-back-legacy and poort universal packaging.
And I'm not positive, but I think Linux might be the same as Windows in that regard.
99% of the time, Linux programs are either fully open source or distributed natively for x64. It's extremely rare to need to do anything 32-bit on a 64-bit system.
Just checking, and I have exactly zero 32-bit binaries or libraries on my Gentoo laptop :D
Just checking, and I have exactly zero 32-bit binaries or libraries on my Gentoo laptop :D
Is that inclusive of libraries included with the OS? As in, your laptop couldn't run an x86 binary if you wanted it to?
I could run a 32-bit binary, but I would need to first install literally every libraries it needs in 32-bit form. So no, not as things stand right now. There are NO 32-bit binaries or libraries, with the possible exception of my bootloader and some bootstrapping portion of my kernel.
And on Gentoo, every program that can be is distributed as source-only, and compiled on the end machine. I don't and never have had a 32-bit capable version of GCC installed.
It's very uncommon for Linux programs that are distributed as binaries to not include a 64-bit version, and even rarer for source-distributed programs to not be 64-bit ready.
I was under the impression that the situation for OS X was somewhere between Windows and Linux.
What if you install Steam games? I was under the impression that there's a fair bit of 32-bit stuff on Steam. (But that might just be me spouting things; I haven't done any fact checking.)
What if you install Steam games? I was under the impression that there's a fair bit of 32-bit stuff on Steam. (But that might just be me spouting things; I haven't done any fact checking.)
The situation has yet to come up for me :D
Previously, on my Fedora machine, Steam just downloaded opaque binaries and libraries for whatever it needed, which either had very odd library settings or were mostly statically linked. Likely to avoid problems like this.
I think the main thing Steam requires to have in 32-bits is SDL.
To the original question my final version wanted the frameworks in a folder called frameworks in the same directory as the app, not inside the package or installed anywhere else. There were earlier versions that wanted them in your user's library folder.
That said I'm not aware of it being tested on anything newer than Neo's snow leopard MacBook, so it may just break on newer machines.