| Re: [AD] 5.0.7 preparations |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Most things work on OS X 10.6.8. These are the issues I ran into with some of the examples (didn't investigate or go back to check whether these were ok with the previous version):
1.
$./ex_audio_chain
dyld: Symbol not found: __al_mangled_main
Referenced from: /Users/eglebbk/Program/Allegro5/5.0.7/wangp-allegro-testing-e8fd52c/Build/lib/liballegro_main.5.0.dylib
Expected in: flat namespace
in /Users/eglebbk/Program/Allegro5/5.0.7/wangp-allegro-testing-e8fd52c/Build/lib/liballegro_main.5.0.dylib
Trace/BPT trap
$
2.
$./ex_fs_resize
Sat Jun 23 22:04:14 morgaine.local Vim[82603] <Error>: kCGErrorIllegalArgument: CGSShapeWindow
Sat Jun 23 22:04:14 morgaine.local Vim[82603] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
$
3.
$./ex_fs_window
2012-06-23 22:05:29.785 ex_fs_window[82644:4103] *** __NSAutoreleaseNoPool(): Object 0x1002518b0 of class NSCFArray autoreleased with no pool in place - just leaking
2012-06-23 22:05:29.788 ex_fs_window[82644:4103] *** __NSAutoreleaseNoPool(): Object 0x1002188f0 of class NSCFNumber autoreleased with no pool in place - just leaking
2012-06-23 22:05:29.789 ex_fs_window[82644:4103] *** __NSAutoreleaseNoPool(): Object 0x100256e10 of class NSCFDictionary autoreleased with no pool in place - just leaking
[snip]
(happens when pressing space to switch from fullscreen->windowed mode)gg"*yG
The first looks like a simple oversight in the Makefile, the 2nd and 3rd may be fixed in 5.1 (again, haven't tested this yet). The third looks like something that should have been fixed by a recent patch though, but it may be something that didn't make it into the backport to 5.0.
Finally somthing I noticed in ex_font_justify: the green line starts under the last stem of the "m" in "ipsum" and ends beneath the i in "sit". I have no idea whether this is actually a problem or not because I don't know what it's supposed to look like.
I personally don't think any of these are show-stopping problems (apart from the first, which is probably a simple fix, everything looks ok on-screen as the program is running).
Evert