Elias Pschernig wrote:
> On Wed, 2007-06-27 at 20:48 +0200, Andrei Ellman wrote:
>> Trent Gamblin wrote:
>>> I had an extra free domain registration that was going to go to waste,
>>> so I registered liballeg.org. It now redirects to Sourceforge.
>>> Subversion is also at svn.liballeg.org. This is not a mirror, just a
>>> redirection. Elias set up the virtual hosting at Sourceforge for it to work.
>> Here's an idea. Perhaps the domain could be a site that hosts the DLLs
>> etc. needed to run dynamically-linked builds of Allegro programs. It
>> would be nice to have a place where you could download alleg42.dll for
>> 4.2.1 (and alleg40.dll for 4.0.3 if you want to run older programs). In
>> fact, if someone is writing a script for an installer that installs a
>> dynamically-linked app, if it detects that Allegro is not installed on
>> the system (or an older version is installed), it could download the DLL
>> from a URL that always stays the same. Of course, if the apps were
>> statically linked, this hassle will be avoided, but sometimes, I still
>> come accross dynamically linked apps built with Allegro 4.0.x.
> I think you want this: http://allegro.cc/files/
That's sort of what I had in mind. However, I notice that in order to
get _just_ the DLL, you need to download the entire pre-built binary
packages. Not only do you get the debug and profile DLLs (when you
probably just want the release DLL), but you also get the libs and
includes. While this is useful for someone who wants to be able to
compile Allegro based programs without building Allegro, it's OTT for
someone who just wants to download a dynamically linked program they
loaded off the net.
I think there should be a zip file that contains the latest version of
the 4.2 DLL (and also one that contains the latest 4.0 DLL) so that
anyone who wants to run a dynamically linked Allegro app can do so with
minimum fuss. Of course, we'd still have to decide on which compiler to
use to build the DLLs.