Author
|
Topic: The UQM MegaMod - Now on MacOS X! (Read 25045 times)
|
|
|
darklord42
*Many bubbles*
 Offline
Posts: 208
|
Heh, Will I bet you apples to dollars it's a clang issue. I'd try the Apple/gcc-4.2 compiler first. That's the compiler that shipped with Xcode3 and is available on macports.
Sure does explain why the windows version worked...
[EDIT]
Hmm applegcc-4.2 doesn't like my system files stuff, I'll have to get a 10.6.sdk and try to link that..
But I'll have to do it after work. VMing an old OS may be the way to go...Apple makes thing unnecessarily hard sometimes...
|
|
|
|
« Last Edit: March 08, 2017, 09:01:47 pm by darklord42 »
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
macports is a linux like package manager for OSX
10.6 I knows works in VirtualBox as I used it for a long time before I borked it.
|
|
|
|
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
Hmm, your going to hit the same problem i'm getting. The problem I'm having is that apple/gcc-4.2 doesn't work with the modern system folder. Installing a full XCode package on 10.10 is just going to hit the same problem. That said you should beable to link the 10.6 sdk with -sysroot /folder/MacOS10.6.sdk as a linker flag (I think). I just tried it with 10.7 sdk as that is what I had in my system currently and no luck either....
[EDIT]
Oh yeah Xcode3 comes with the right SDK. So use that!  it will be in the /Developer folder
|
|
|
|
« Last Edit: March 08, 2017, 09:40:39 pm by darklord42 »
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
For the record, I built it with clang 3.9 and had the same result. I wanted to try it with a modern gcc, but the buildscript makes it dang hard, for a few reasons. A) it wants to use frameworks in the system folder and not dylibs and B) It detects osx and wants to use some osx objective c stuff (there is some sort of osxmsgs.m file) ...Neither of which work with gcc.
So therefore the only gcc we can use is apple's ancient gcc4.2. Longstory short, I really need to setup my 10.6 virtualbox VM. I think that's the only way we can get this to work. What a pain...
Thankfully I still have my 10.6 server image which is I think the only one that works with virtualbox, but it's still going to take a bit of doing to get everything setup.
I suppose I needed it for a future project anyway. I compile with 10.6 as the easiest way to maintain compatibility with that system. On the plus side, the binary will support 10.6+ if nothing else.
|
|
|
|
« Last Edit: March 09, 2017, 06:13:37 am by darklord42 »
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
Just so you know, 10.6 had the Xcode we need right on the install disc under other installs. So you don't have to register as an apple dev and download it off their site.
|
|
|
|
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
Excellent! with Xcode 3 you are most likely using said apple gcc. I wouldn't say it's entirely clang's fault, but it is a very pedantic compiler. GCC historically lets you get away with more. Unfortunately these bugs are the kind that don't make the software crash or build incorrectly, and the very hardest to fix...
Chances are pretty good it will work with Sierra, I have stuff compiled for 10.6 that still work for 10.12. As long as it's not built for PowerPC... Which you don't have.
|
|
|
|
« Last Edit: March 09, 2017, 02:06:22 pm by darklord42 »
|
Logged
|
|
|
|
|
|
darklord42
*Many bubbles*
Offline
Posts: 208
|
Unfortunately I believe PearPC's development has been pretty slow. I never tried to get it to work. Did have sheepshaver running till I resurrected my old beige G3
|
|
|
|
|
Logged
|
|
|
|
|
|
|
