| Re: [AD] build process overhaul |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Monday 26 December 2005 17:32, Jon Rafkind wrote:
> >Does your build system correctly detect the precense of 64 bit CPU's?
>
> Not really. There is platform.processor() from python but this doesnt
> tell you explicitly if you have a 64-bit cpu, it just returns a string
> which is the name of the processor like "Pentium III( Copermine )" on my
> system. The current checks for an intel cpu, amd cpu, or sparc cpu are
> assembly programs hardcoded into the build system. I guess someone could
> write checks for 64-bit cpus as well.
There is one in the configure script. Without it Allegro doesn't build
correctly on 64 bit systems.
> 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.
Evert