| Re: [AD] proposed patch for nicer asm symbols exports |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wednesday 04 August 2004 16:01, Sam Hocevar wrote:
> I would like to get rid of alleg_unsharable because its presence
> means that you can only upgrade liballegro in a way that works with all
> previous versions of alleg_unsharable your binaries were compiled with,
> or you have to recompile all your applications, which kinda defeats the
> purpose of shared libraries.
That sounds reasonable, but: Allegro WIP releases are not guarenteed to be
ABI compatible, only stable releases are.
Still, getting rid of it is not such a bad thing IMO, especially if it
means getting rid of the magic main.
> On Debian systems, I have removed the need for alleg_unsharable,
> and the main() routine I posted to the END_OF_MAIN thread provides a
> compatibility layer for previous or third-party allegro-using binaries.
You may be pleased to learn that I /think/ I have found a (reasonably)
portable way to eliminate the need for the magic main while retaining the
function of get_executable_name() across different flavours of UNIX.
I haven't finished my patch yet (although I have the extra configure checks
needed in place and tested), but preliminary results suggest that it will
work at least on Linux, Solaris and Irix, (and probably other System V
complient systems). I hope to have it done tomorrow.
If it checks out ok, then main() can be removed from alleg_unsharable.
Evert