| Re: [AD] No need for END_OF_MAIN (Windows) |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] No need for END_OF_MAIN (Windows)
- From: Hrvoje Ban <spoofer255@xxxxxxxxxx>
- Date: Sun, 15 May 2005 20:22:45 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uh0eN6vfUpxEbGt01Xq+gE69LnIJ5Hte2zawm+nzNilJlB2TGXwlGLehPPHuxR3TQfwOuIZZeqf1v1VtwfZHpgt74vQU3nYFs3CzQMIPdK1mm4qk5c2lTVPqWQX+32o5rcxmFM+AKK/gAycVEhskqlY76/kU72FXYrRWOCPKOuY=
> I mean that liballeg.so should not be referencing missing symbols that
> have to be supplied by the user. It's a pain to load liballeg.so
> dynamically if you have to provide a _mangled_main to be resolved.
> Moving the definition of main()/WinMain() to, say, a libalmain.a would
> get rid of this missing reference, at the cost requiring most users to
> have to link with -lalleg -lalmain instead of -lalleg
Can't additional object code be appended to libraries, that is adding
WinMain code to already created liballeg.a