Re: [AD] MacOS X shared library

[Eric Botcazou <ebotcazou@xxxxxxxxxx>]

> I have made some changes to the makefile so that when creating Allegro
> as a shared lib, it is split into two chunks, like under Unix: the
> shared lib itself, which has no undefined symbols, and a very small
> static lib named liballeg-main.a, which just has the real main()
> function that refers to _mangled_main. This way when calling
> allegro-config both libs are linked in and no problems arise, and
> addons could just link to the shared (now prebound!) chunk risking no
> errors. The only "bad" thing in this I can see is the fact we now have
> two libs, and some other things have to be updated (like the
> ProjectBuilder app template, which should now link to alleg-main, and
> the enduser package docs, which should report that it doesn't contain
> alleg-main, thus it can't be used to code, but just to run third party
> Allegro apps)

Are these changes limited to the MacOS X port?  If so, I don't see any 
problems on principle with them.  But, of course, having a patch to look at 
would be far more reassuring :-)

-- 
Eric Botcazou