RE: [Allegropro-dev] Updates to CVS/new file release

[Korval <Ko...@co...>]

I got some fairly negative response to the idea of having to distribute an
executable to be able to build AllegroPro as well. Some people don't like
the idea of distributing executables, and, as Bob pointed out, it really is
only for building makefiles and projects.

-----Original Message-----
From: all...@li...
[mailto:all...@li...]On Behalf Of
Peter C O Johansson
Sent: Wednesday, September 22, 2004 5:42 AM
To: AllegroPro
Subject: Re: [Allegropro-dev] Updates to CVS/new file release



> OK, nevermind. I got it now. So why don't we have this Premake project
> in the zip so the user won't have to dowload Premake?

I think because it is not a requirement in order to compile AllegroPro.
All you need as an end-user is the makefiles generated by Premake, and
these can easily be generated and bundled prior to release. Premake is
really only of interest to people working on AllegroPro, and would add
bloat to an end distribution.

--
Peter C O Johansson



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Allegropro-development mailing list
All...@li...
https://lists.sourceforge.net/lists/listinfo/allegropro-development