| Re: [AD] custom DLLs with cmake |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] custom DLLs with cmake
- From: "Matthew Leverton" <meffer@xxxxxxxxxx>
- Date: Wed, 24 Dec 2008 12:08:31 -0600
People will distribute incompatible DLLs, and it will cause problems.
That much is certain. But I don't think it's that big of a problem.
Allegro.cc and SF will always host the official DLLs, so if somebody
gets messed up, they can be instructed to download them. It will
happen.
However, I think people should be STRONGLY encouraged to use the
binary builds of Allegro for Windows. There's no point in building and
distributing custom DLLs with missing features. Nobody should be that
concerned over saving a few KBs.
That said, I think empty stubs should be a requirement for any
function (core or add-on) that could potentially be disabled.
--
Matthew Leverton
On 12/24/08, Elias Pschernig <elias.pschernig@xxxxxxxxxx> wrote:
> On Wed, 2008-12-24 at 16:20 +0200, Milan Mimica wrote:
>> 2008/12/24 Milan Mimica <milan.mimica@xxxxxxxxxx>:
>> >
>> > It won't link on MSVC as allegro.def contains both D3D and OGL
>> > symbols. This is the real reason behind this "feature".
>>
>> Correcting myself: It's an issue with any compiler on Windows, not just
>> MSVC.
>>
>
> I see. Best solution likely is to provide empty placeholders for all
> functions in allegro.def then if they are disabled.
>
> --
> Elias Pschernig <elias@xxxxxxxxxx>
>
>
> ------------------------------------------------------------------------------
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>