macosx/OpenTyrian.xcodeproj/project.pbxproj seems to be outdated

[GoogleCodeExporter]

Please provide any additional information below.
macosx/OpenTyrian.xcodeproj/project.pbxproj contains references to all .c 
files, but it doesn't contain any reference to (the quite recently added) 
video_scale_hqNx.c.
Hence, I suspect that this way of building doesn't currently work (I don't have 
a Mac so I can't verify this).

Original issue reported on code.google.com by a.h.vand...@gmail.com on 17 Jul 2010 at 6:25

[GoogleCodeExporter]

Unfortunately, this is a reoccurring problem because none of the developers 
have Macs either.  If somebody with a Mac wants to submit an updated project 
file, we would appreciate it.

Original comment by mindless...@gmail.com on 17 Jul 2010 at 3:04

• Changed state: Accepted
• Added labels: OpSys-OSX

[GoogleCodeExporter]

I suppose it's a good idea to add something about building OpenTyrian to the 
README, indicating which ways are supported ("make"), and which are provided 
"as is" ("xcode").
Or, if no one submits an updated project file, maybe the macosx directory 
should just be removed instead...
By the way, the current win32 binary under "Downloads" is somewhat old, making 
bug reports from windows users less useful (since their bugs may simply no 
longer exist in the current code). Hence I suggest to update it (maybe this 
should be done automatically after each new revision is pushed, as long as hg 
tip builds succesfully?)

Original comment by a.h.vand...@gmail.com on 19 Jul 2010 at 9:36

[GoogleCodeExporter]

Hm, is the new win32 binary from a hg revision that hasn't been pushed to the 
main repository yet or am I missing something?

Original comment by a.h.vand...@gmail.com on 19 Jul 2010 at 5:21

[GoogleCodeExporter]

Oops, I was still pushing the Windows builds on to my old host.

Original comment by mindless...@gmail.com on 19 Jul 2010 at 9:57

[GoogleCodeExporter]

But what hg revision was the most recent binary (201007191233) built from? The 
titlescreen says "Classic (e51ff32e4877 default)", and I usually use this 
information to pull the sources that correspond with the binary (hg pull -r 
<revision>), but this time I can't seem to find this revision in the googlecode 
repository. Was the binary built from a revision that's not yet in the 
googlecode repository?

Original comment by a.h.vand...@gmail.com on 20 Jul 2010 at 7:06

[GoogleCodeExporter]

Oops (again), I was trying to be clever by keeping my auto-build script in a 
Mercurial Queue; I didn't think about that ruining the revision information.  
I've uploaded another build which should be identical to the last one except 
for the revision number.  Good catch!

Original comment by mindless...@gmail.com on 20 Jul 2010 at 12:40

[GoogleCodeExporter]

I have a patch for this: 

Original comment by fda...@gmail.com on 14 Aug 2010 at 10:41

Attachments:

• MacBuildFix.bundle

[GoogleCodeExporter]

Committed as r3f3819c0b2.

Original comment by mindless...@gmail.com on 16 Aug 2010 at 11:25

• Changed state: Fixed