The Glider PRO source was released a few years ago, and for someone wanting to get into programming a bit and make something useful, I was hoping to compile it and reverse engineer it, but the files seem to be designed for CodeWarrior for Mac. The archive contains CodeWarrior Pro 6 for Windows, which might be more useful for the modern age (I use Windows for gaming now, and I want to bring classic Mac games out from being locked away in SheepShaver) but I don't know if it will work for modern PCs or not. There's no instructions on how to compile Glider PRO for anything, almost is if the files were just rescued from an ancient hard drive somewhere.
This page is a wiki. Please login or create an account to begin editing.
2019, June 13 - 1:12am
#1
Porting Glider PRO to modern systems
Comments
2019, June 13 - 4:19pm
#2
CodeWarrior Pro v6 Mac could build 68K, classic PPC and OSX binaries. It won't create Intel binaries.
I think CodeWarrior development ceased before Intel binaries were invented.
Gary
2019, June 13 - 11:22pm
#3
CodeWarrior for Windows installed and recognized the code but still produced 150 errors. I think it's definitely possible but not all that easy. I'll keep in touch.
2019, June 14 - 4:03pm
#4
Codewarrior for Windows when installed on a Mac will create Windows apps. They can't be tested on a Mac unless a Windows emulator is installed.
If you try to compile code intended for Windows but with Mac libraries in the project, Codewarrior will try to compile the code but will fail.
Gary
2019, June 14 - 5:20pm
#5
The Glider PRO code is intended for (classic) Macs but I'm trying to run it for Windows (with a Windows version of CodeWarrior). As expected, CodeWarrior (from 2000) did not run the code as-is, and produced 150 errors, some of which seem to be exclusively how CodeWarrior handles things.
2019, June 15 - 12:41pm
#6
This is an "Apples" vs. "Oranges" situation. In your example error the call to "GetCursor" is a reference to a Mac Toolbox system call. Windows has no such routine in its system library. Thus if you want the call to resolve correctly, you will need to write your own "GetCursor" that calls the routine that Windows uses to get the cursor definition.
Writing such a library (for all 150 calls in your project) is a HUGE task.
It's been done by others. For example engineers at Adobe developed such a library when they released Photoshop in the 80s. Their library let them code for both Windows and Mac using the same lines of code. They also did it in C++ using the MacAPP framework.
Gary
2019, June 15 - 8:05pm
#7
This is what was supposed to done with MEAD, a project 10 years ago that was actually started by someone who liked the idea I had--it was to translate Macintosh system calls to modern systems. I pulled out my old Inside Macintosh Volume I and refers to the GetCursor calling CURS from the toolbox. I'm not going to run down for VI but at some point, it was replaced with crsr, which is the resource where the color cursors are kept. But at the same time, it's not an especially obscure call that needs extensions to work properly. I'd be surprised that there's not common libraries that were used for porting, like custom DLLs, or if a DLL could be "borrowed" from another source.
2019, June 14 - 2:10am
#8
Would you be interested in porting glider to a commercial game engine?
I'm currently doing EVO in Unity3D. I can help you with Unity if you are interested.
A few dev videos@
http://twitch.tv/nilobject
2020, November 11 - 11:53pm
#9
Hi,
Back here for the first time in several years !
I saw your your message and was indeed interested to start a port, got to the project's sources on github and... someone already did it, getting way further than I would ever have : https://github.com/elasota/Aerofoil
Enjoy !
2020, November 14 - 8:08am
#10
Already in a different thread: