[AD] MacOS X compatibility and WIP |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I finally finished installing Panther (OSX 10.3), its developer tools
(gcc 3.3) and all the application that make my life easier under this
beautiful platform.
Anyway, I've been able to test if Allegro works here, and it does... It
also showed me a little memory leak in hidman.m that Jaguar wasn't
reporting; I already fixed it.
As for WIP release: the showstopper was the 10.1.x compatibility. Well,
so far I still have got no replies on the issue, so it is either noone
in the mac community is using Allegro, either no mac developer still
has 10.1.x... In any case, I propose we drop source compatibility with
10.1.x: the lib binary will still work under 10.1.x normally, but to
compile it you'll need 10.2.x.
It is a first step to move away from 10.1; if we ever completely drop
support for it in the future, chance is we could make the library port
slimmer, as to make Allegro work under 10.1.x, I had to use Carbon
hacks. Under Jaguar you can do the same things cleanly in Cocoa, thus
we could remove the need for Carbon. Just a thought...
What do you think? If we drop source compatibility with 10.1 all I'd
have to do is to update the docs and we could release the WIP for me.
--
Angelo Mottola
a.mottola@xxxxxxxxxx