On Wed, 04 Feb 2015 09:26:37 +0000, eles wrote: > On Wednesday, 4 February 2015 at 05:35:44 UTC, ketmar wrote: >> On Tue, 03 Feb 2015 17:33:53 +0000, Russel Winder via Digitalmars-d >> wrote: > >> in no way ready for public usage. > > In the context of this discussion, if you can spare 5 or 10 minutes, it > could be useful if you could provide a more detalied description of the > tool and the constraints/choices that you had to do.
actually, i'm using a heavily modified fork of jam[1]. i don't want to advertise it, though, 'cause it's very "ketmar-specific", and i have no plans to make it usable for anyone who has some different views on build process. ;-) > I kinda was always looking for the perfect build system and messed with > make, cmake, scons, waf, fbuild (https://github.com/felix-lang/fbuild), > boost.build, biicode etc. > > Yes, not much ant, maven or gradle. you can look at it here[2], but beware! it's not very well documented, it's incompatible with any other jam fork out here, and it doesn't contain ALL changes. ;-) i was looking for good build system too, and jam was the one that *almost* fits my needs at the time. then i started to fix some things there, adding some things, and so on. i was never trying to write yet another "universal build system for anyone", it's just a tool for me and my friends (yes, it actually has other users except me! ;-). i dropped windows support some time ago (just don't need that, 'cause i'm doing cross-compiles from GNU/Linux anyway) and added 'k8jam config' supporting scripts, which does some checks that 'configure' does. it may work on non GNU/Linux OSes, but i never check that ('cause i don't need that ;-). [1] http://en.wikipedia.org/wiki/Perforce_Jam [2] http://repo.or.cz/w/k8jam.git
signature.asc
Description: PGP signature
