michipili

Hi Volker, thank you for your posting! These are good ideas, I should definitely complete my text with such examples.

Also, I forgot to point out, I have an autoinstall script for bmake and bsdowl, it is here:

     https://github.com/michipili/anvil/blob/master/subr/anvil_travisci_autoinstall.sh

It will install both of them under ~/.local, so that you need to tweak your path accordingly, but you can choose another prefix with the `-p` flag, like

  sh anvil_travisci_autoinstall.sh -p "${HOME}"

If you want to customise it, you can trim most of the script (autoinstall_opam*) because you do not need this. :) And if you need something more specific, just ping me on the issue tracker for instance. :)

michipili

11 anni fadiscuss

You can bribe your colleagues by showing them how cleanly it handles LaTeX documents and METAPOST figures, in case they use METAPOST for their technical drawings. :) And the clean target leaves everything you need to send your file to an editor (i.e. it does not remove bibliography files, index, and figures, which are removed by a more powerful realclean command.)

michipili

11 anni fadiscuss

bmake is very portable and it is available on Debian and Ubuntu. I am not aware of any RPM package but installing from sources is a breeze, I had it running on the newest CentOS as well as on paleontological Solaris editions, without having to tweak a single line of code.

If you look for a more engineered installation solution, give a try to PKGSRC, which is the (portable) ports tree of NetBSD – though I never used it intensively. This even used to work in a (now obsolete) Unix-like environment on windows.

When you'll find time to experiment with the Makefiles, feel free to get in touch (my email is in the source, or with the issue tracker) I will be happy to help.

michipili

11 anni fadiscuss

Thanks! Also note

1) It currently supports M4 and provided that there is a simple rule to infer the name of the preprocessed file from the name of the unprocessed file, it would be easy to add another one, see [1].

It is also possible to support more complicated source generation tools, like literate programming tool. We currently have support for noweb [2] which could be used to derive more.

  [1] https://github.com/michipili/bsdowl/blob/master/bps/bps.m4.mk
  [2] https://github.com/michipili/bsdowl/blob/master/bps/bps.noweb.mk

2) I would say, they are not difficult to write, but these are Makefile, and programming Makefiles is a mindset on its own, because we never write the “glorious high-level procedure doing plop-plop fuzz-fuzz on all our files” but just move from one step to the other and must save all state in inodes. :) The folder `bps` contains code which is shared by all frameworks (langc, texmf, ocaml, script).

3, 4) The system supports two variables ARCHITECTURE and CONFIGURATION which are used to selectively include a configuration file to tweak flags (like debugging, profiling, cross-compiler chain and the like) and which can be used to tweak the directory where compilation products are stored. Once it is setup it just looks like

     bmake ARCHITECTURE=Mingw32
     bmake ARCHITECTURE=Native CONFIGURATION=Release

You can see a small example in the example/langc/heat directory [3]

  [3] https://github.com/michipili/bsdowl/tree/master/example/langc/heat

michipili

11 anni fadiscuss

This is a fair point. :) That said, it works on more that what is advertised. At the time of writing it also worked on the current branch of NetBSD, and OpenBSD provided you install manually a modern version of bmake.

It also used to work on Cygwin, but I am not sure of the current status.

michipili

11 anni fadiscuss

Of course grepping log is terrible! Grep is a generic tool, why shouldn't it be defeated by specialised tools?

http://unix-workstation.blogspot.de/2015/05/of-course-greppi...

Submissions

DevOps Stack Exchange proposal moved to commitment phase

DevOps Q&A proposal reaches 200 followers on stack exchange

DevOps proposal on Stack Exchange to reach 100 followers

comments