Follow-up Comment #9, bug #11707 (project wesnoth):
After my observations in comment #8, I rebuilt wesnoth, this time as a disk
image and without debug info; while the binary was the exact same size as the
one from the official package, it has a different checksum, and -
significantly - has not crashed with the described effect yet.
Sources: Wesnoth 1.4.2 source package from the main page + "Mac Compile
Stuff" folder from the 1.4.2 DMG (again from the main page) + some hacks to
the XCODE project file:
- use libfreetype.a from the 10.4u SDK (NB I did not do as suggested in one
of the mac-install forum threads, by copying the 10.4u libfreetype.a into the
10.5 folder, but rather editted the project file to grab this file from 10.4u
specifically...)
- some paths in the project file changed from /sw to /opt/local (I use
'ports' rather than 'fink' - or at least have done so so far)
- removed the /opt/local/lib library include (possibly this was /sw/lib
originally...)
The compile ran through more or less cleanly (a handful of warnings, but
nothing to dramatic sounding).
Observed differences to the "official" binary:
- No crashes :P (at least not tonight)
- The "gong" sound described in comment #3 no longer comes (one case where it
was almost reproducibly coming was when pressing command+s for the save menu,
for example).
- The wesnoth map which appears during the HttT scenario stories is scaled
differently - previously it was scaled to fit the whole window (at 1920 wide
* approx 1024 high... an oddish resolution, to be sure), ignoring aspect
ratio; now it no appears to no longer ignore the original aspect ratio (it
fills the window verticaly, but not horizontally). Note that the wesnoth map
on the title screen is still scaled to fit the whole window. I suppose it's
at least possible that this is a red herring - maybe I'm hallucinating, or
maybe the briefings I've seen this evening have been set up slightly
differently (I'm progressing along the HttT story line ,p).
Now, the latter two points of difference above may or may not be significant,
but it does strongly suggest that the binary I've built is more than a little
different from the official package.
Which raises the question: why? Is it just because my build environment (dev
libraries etc) is a little different to that of the official package
maintainer, or what?
Should I attach the DMG I generated, or some paticular part of it?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?11707>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
