Re: Mac OS X porting help wanted
- From: Jeff Lait <torespondisfutile@xxxxxxxxxxx>
- Date: Sun, 13 Jan 2008 17:05:33 -0800 (PST)
On Jan 13, 7:36 pm, "copx" <c...@xxxxxxxxx> wrote:
"Jeff Lait" <torespondisfut...@xxxxxxxxxxx> schrieb im Newsbeitragnews:af067997-7c63-46f1-98f7-967ff8ba21a0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Okay, I checked out the latest source from the sourceforge site.
make -f mac.mak
fails because it can't find "sources.inc". I took a wild guess and
changed the makefile line to wrogue_sources.inc and recompiled. I
think you might have a symbolic link in your environment?
No, the makefile was simply outdated.
In that case you need to create a symbolic link
sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o /Developer/
SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o
This might solve the linking problem than.
******
Another outdated part of the makefile I guess. I have idea, really. I did
not write that makefile, and I know nothing about Mac coding.
Okay, now at least you can update those parts of the make file :> The
second problem might not be an issue with the makefile, it might just
need to be something in the build.txt file.
Making that change lets me compile into a wrogue binary.
To build a dmg, I do
make -f mac.mak dist
Voila! I have a wroge-0.8.0.dmg. Unfortunately, I don't have the
slightest clue if it does anything useful as I just have console
access to aforementioned mac :>
I am amazed that it compiled without source changes.. Not just the makefile
is outdated, the platform code is outdated too. It needs to modified to work
as expected.
Well, it compiled. I haven't actually tried running it.
If this suffices for your purposes, I can do such an update/build on
demand. What I can't do is actually test the binary.
Thanks a lot, but I am uncomfortable with the idea of releasing that
package. Warp Rogue has the worst possible rating at a certain Mac games
site simply because the DMG of the first Mac release was not built
perfectly. The porter used a compression algorithm not supported by older
versions of Mac OS X, and the guy was a Mac programmer..
I mean, packaging for OS X is tricky and Mac users are not like Linux users.
They expect everything to work perfectly out of the box. I do not want to
ruin Warp Rogue's reputation even more by publishing such an "unsafe"
package.
Can't say I blame you for wanting caution. Thanks for the tip
re: .dmg compression - I copied your makefile so I should probably
double check that UDZO compression string. Does your current .dmg
compile in a friendly way, or will POWDER be sharing WarpRogue on said
sites most hated list?
I think, BTW, it speaks very poorly of such site that the rating of a
game should depend on the rating of the packaging. How much more
superficial can they get? The real culprit, IMHO, is Apple. It
should not be possible to have a .dmg that can't be run on older
versions of OSX. OTOH, my brother in law just had to switch to
Windows because he bought a new iPod and the new iPod refused to work
with his older version of OSX.
I really wish I had Steve Job's mind control powers.
--
Jeff Lait
(POWDER: http://www.zincland.com/powder)
.
- Follow-Ups:
- Re: Mac OS X porting help wanted
- From: copx
- Re: Mac OS X porting help wanted
- References:
- Mac OS X porting help wanted
- From: copx
- Re: Mac OS X porting help wanted
- From: Jeff Lait
- Re: Mac OS X porting help wanted
- From: Jeff Lait
- Re: Mac OS X porting help wanted
- From: copx
- Mac OS X porting help wanted
- Prev by Date: Re: Mac OS X porting help wanted
- Next by Date: Re: Mac OS X porting help wanted
- Previous by thread: Re: Mac OS X porting help wanted
- Next by thread: Re: Mac OS X porting help wanted
- Index(es):
Relevant Pages
|
