S
scholz.lothar
What is the best build tool for somebody who want to get rid of make.
I'm looking for something with the following features:
1) Must scan the files for dependencies.
2) Results from 1 must be safed so that not each invokation is doing a
complete scan because the files may be on a NFS with slow connections.
3) Should do a preprocessing run and check if there are real changes.
If i change code
4) Collects compile optinos in a database/central location so i don't
need to set them in a lot of
build files.
5) Works well with multiple CPU's/Core's and ideally detects the
number of available CPU's
automatically. Running it on a nightly build machine with 1 cpu or a
developer machine with 8.
6) As 5 suggests. I need a good split into independent dependency
targets. Aka "make -j"
7) Does not need huge requirements to work: No Java solution (and no
Perl). ANSI C with a few Posix/Plattform Hacks would be best. But ruby
or python based are also okay.
8) Helps me to avoid autoconfig/automake hell.
9) Available on WinXP/WinVista/FreeBSD/Linux/NetBSD/OpenBSD/Solaris/HP-
UX/MacOSX is required. All in 32 and 64 bit modes (BSD's and Linux
will hot have a 32 bit library installed)
10) Fast.
11) Little typing.
I heared about jam and will start reading the docs tomorrow. So please
comment. I only worked with make in the past.
I'm looking for something with the following features:
1) Must scan the files for dependencies.
2) Results from 1 must be safed so that not each invokation is doing a
complete scan because the files may be on a NFS with slow connections.
3) Should do a preprocessing run and check if there are real changes.
If i change code
4) Collects compile optinos in a database/central location so i don't
need to set them in a lot of
build files.
5) Works well with multiple CPU's/Core's and ideally detects the
number of available CPU's
automatically. Running it on a nightly build machine with 1 cpu or a
developer machine with 8.
6) As 5 suggests. I need a good split into independent dependency
targets. Aka "make -j"
7) Does not need huge requirements to work: No Java solution (and no
Perl). ANSI C with a few Posix/Plattform Hacks would be best. But ruby
or python based are also okay.
8) Helps me to avoid autoconfig/automake hell.
9) Available on WinXP/WinVista/FreeBSD/Linux/NetBSD/OpenBSD/Solaris/HP-
UX/MacOSX is required. All in 32 and 64 bit modes (BSD's and Linux
will hot have a 32 bit library installed)
10) Fast.
11) Little typing.
I heared about jam and will start reading the docs tomorrow. So please
comment. I only worked with make in the past.