Re: [AD] build process overhaul |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2005-12-26, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> On Monday 26 December 2005 17:32, Jon Rafkind wrote:
> > plugins.h isnt used anywhere except for tools/datedit.c and plugins.h
> > for every platform is just
> > $ cat tools/plugins/*.inc > plugins.h
> > so why not just cat them into wherever the tools are going to be built
> > and do #include "plugins.h" instead of #include "obj/platform/plugins.h"
>
> Why not indeed? Does Anyone know?
> I always assumed that there was a good reason for having a plugins.h
> sitting in obj/platform/ but now I can't really think of any except for it
> being a generated file... which doesn't strike me as much of a reason,
> actually.
One reason could be line endings. If you have one Allegro working
directory shared between Windows and Linux then a plugins.h generated
under Windows could have line endings that gcc on Linux doesn't like.
Peter