[ros-kernel] Would it be feasible to use automake/autoconf?

Casper Hornstrup chorns at users.sourceforge.net
Sun Dec 28 18:47:04 CET 2003

> -----Oprindelig meddelelse-----
> Fra: ros-kernel-bounces at reactos.com 
> [mailto:ros-kernel-bounces at reactos.com] På vegne af Daniel Benoy
> Sendt: 28. december 2003 17:52
> Til: 'ReactOS Kernel List'
> Emne: [ros-kernel] Would it be feasible to use automake/autoconf?
> I just discovered the ROS project and I was very excited to 
> start playing with 
> it, but compiling the source was messy and unpleasant.  I 
> wonder if it's 
> feasible to get the ROS source using automake/autoconf so it 
> can have a 
> traditional ./configure script.
> Assuming it's done with the proper care, it would vastly increase the 
> simplicity of the compilation process.. (and goodness knows how many 
> developers out there wern't as patient as I, and simply left 
> the project 
> before even joining)
> Would such a scheme cause problems for developing under 
> windows?  Are there 
> other problems I don't see?

I kind of like that you need very few tools to develop on ReactOS
(GNU make+mingw+nasm). I don't see how autoconf will make the process
any simpler. Currently you need to just run 'make' from the top-level
reactos directory to build ReactOS.

Autoconf is useful for testing for specific features of the platform
where you perform the build (cross-compiling is usually very difficult
with autoconf, but I won't go into that here).
For ReactOS, this has little use since we have very few tools that need
be run on the build platform. Most components are build for the ReactOS
platform and we already know what features this platform supports since
we build the platform ourselves ;-)

Casper Hornstrup

More information about the Ros-kernel mailing list