mkmed automatically generates package build scripts and related files. Unlike make, mkmed works bottom-up, so it can infer information you would otherwise have to specify explicitly.
This package is discussed on the mkmed list. New releases are announced on the prjware-announce list.
mkmed is devoid of warranty and is distributed under the GNU General Public License, version 2. But that doesn't mean it's necessarily a good idea for you to distribute modified versions. (That includes repackaging.) I'd like to know if you plan to do that.
This link always points to the latest version (currently 2020.04.24).
Older versions are published for historical interest.
You can get the latest development sources with:
$ git clone git://git.dogmap.org/mkmed.git
To build and run mkmed, you need my prjlibs
package. Edit conf-compile/depend_* as necessary during
installation. To run mkmed, you also need
GNU Guile.
slashpackage is a good thing. You can
read more about it
here. If you don't already have /package, create it (on any
filesystem you like, as long as it's accessible by the name
“/package”):
# mkdir -p /usr/local/package # ln -s /usr/local/package / # chmod +t /package/.
Then run sp-install:
# sp-install mkmed-VERSION.tar.bz2
Or, if you like to do things manually, unpack the tarball and run
package/install:
# cd /package # bunzip2 < /path/to/mkmed-VERSION.tar.bz2 | > tar -xpf - # cd prog/mkmed-VERSION # package/install
Read package/README and package/INSTALL for
more detailed instructions.
Very incomplete.
mkmed program generates build
scripts and related files.
mkmed-tar program creates a
tarball of a package version.
mkmed-version program
creates a new package version based on an existing version.
#include directives may fail,
or may include the wrong file. Workaround: arrange your files so that no
file includes another file from a different directory.
-lsocket -lnsl" on Solaris).
package/check script.