[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Well, no :)
Static linking will produce a library useful for your environment. If
Allegro builds the static lib with /MT, then all libraries linked to
your program (including your program itself) must also be compiled with
/MT.
This is fine because there's no multi-compiler crossover here.
Sorry, I haven't been following this thread too closely to notice that
you were only referring to the static build of Allegro.
-----Original Message-----
From: alleg-developers-admin@xxxxxxxxxx
[mailto:alleg-developers-admin@xxxxxxxxxx] On Behalf Of Milan
Mimica
Sent: Tuesday, February 01, 2005 12:16 PM
To: alleg-developers@xxxxxxxxxx
Subject: Re: [AD] AMD64 patch
Robert Ohannessian wrote:
> Allegro must always compile with /MD (or /MDd) with MSVC. If not, then
> we break binary compatibility with the Mingw build -and- we break the
> build of all DLL add-ons that use Allegro functions.
>
> Allegro does not handle multiple heaps at all.
So, having STATICRUNTIME env. variable set generates broken lib?
--
Milan Mimica
http://www.nista-pametno.da.ru
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
--
https://lists.sourceforge.net/lists/listinfo/alleg-developers