Very interesting! We've been looking for a better build system. When the time comes, I'll definitely have a look.
Do you think that (c)redo fills all the (non pathologic) use cases of make? --phone is hard. On Mar 19, 2016 5:53 PM, <drwi...@drwilly.de> wrote: > I would like to take a moment of your time, and point you to a little > bit of software that I've been working on recently. > I am not sure if this list is exclusive to Laurent Bercot's software, > but given that my project uses skalibs and the overall appreciation of > djb software here I thought you might be interested anyway. > > What I have been working on is an implementation of djb's redo, which I > have dubbed 'credo' (because it's implemented in C, you know?) > > https://github.com/drwilly/credo > https://cr.yp.to/redo.html > > djb's design notes for redo have existed for quite a while now, > unfortunatly he never released the program itself. > This led to several implementations of it. However all of them seem to > have been abandoned somewhere along the way for reasons unknown to me. > So I decided to explore this topic myself. > > redo is a build-system best comparable to the classic 'make' found on > just about any UNIX there is. > Unlike make however redo is very simple in it's design. > I have to admit that documentation is a little scarce at this point. On > the other hand due to redo's simplicity you don't have to read through > megabytes of html, because there just is no arcane syntax to > understand in the first place. > redo is just plain sh with 3 parameters and it's stdout redirected to > your build target. (in fact sh is just the default - you can use > whatever language you like to write build-scripts) > I believe djb's notes and the *.do scripts in the credo repository > should be enough to get you started. > > credo is currently in a v0.x stage. That means some mallocs still go > unchecked, because at the moment I'm mostly concerned with getting the > things right that djb left open, most notably the way build-dependencies > are stored. > That said, I am using credo for a few other projects of mine, including > a Java and some LaTeX projects and of course credo itself. > Therefore I think credo is now ready for an educated audience. > > I'm interested in any kind of feedback, but I'm hoping to get some > feedback with regard to the compatibility with systems other than linux. >