Subject | Re: [IB-Architect] First impressions |
---|---|
Author | Jan Mikkelsen |
Post date | 2000-07-27T04:04:42Z |
[ On autoconf ]
And so the branching begins ...
I don't see any good reason why the build environment should require a Unix
environment to the extent that GNU autoconf does, and I haven't seen any
real argument for it other than "lots of other people do it that way".
There is also the philosophical problem with the source code which I
mentioned in my first email: The source code trys to know exactly what
capability is present on every platform. For example, aio_* calls are
assumed to work on Solaris and Linux. HPUX is assumed to not have them.
With the code in this state, there isn't much that autoconf buys you in any
case.
There is lots of work to do here. I have little interest in making more
work by trying to emulate GNU projects. At the moment there isn't even a
working makefile.
Jan Mikkelsen
And so the branching begins ...
I don't see any good reason why the build environment should require a Unix
environment to the extent that GNU autoconf does, and I haven't seen any
real argument for it other than "lots of other people do it that way".
There is also the philosophical problem with the source code which I
mentioned in my first email: The source code trys to know exactly what
capability is present on every platform. For example, aio_* calls are
assumed to work on Solaris and Linux. HPUX is assumed to not have them.
With the code in this state, there isn't much that autoconf buys you in any
case.
There is lots of work to do here. I have little interest in making more
work by trying to emulate GNU projects. At the moment there isn't even a
working makefile.
Jan Mikkelsen