Home

This package provides a set of M4 macros to use with autoconf to detect Boost and its various libraries.

Install instructions: All you really need is a single file, boost.m4

Read the README or fetch the latest revision:

wget http://github.com/tsuna/boost.m4/raw/master/build-aux/boost.m4

Then add boost.m4 in the directory where you store m4 macros for your project.

You may also want to run the entire test suite of the project, particularly the first time you use it on a new platform.

git clone git://github.com/tsuna/boost.m4.git && cd boost.m4

./bootstrap && ./configure && make all check

LICENSE

Short story: code released under GPLv3+ WITH EXCEPTIONS to allow you to
incorporate it in any kind of software. The exception reads:

Additional permission under section 7 of the GNU General Public
License, version 3 (“GPLv3”):
 
If you convey this file as part of a work that contains a
configuration script generated by Autoconf, you may do so under
terms of your choice.

Long story:
One of the most common concerns (and I received several mails on this topic)
is that the code is GPLv3+ and people often want to incorporate boost.m4 in
software with more restrictive (read: incompatible) licensing terms. I was
originally waiting for the FSF to release official clauses for GPLv3+
exceptions to re-use them in boost.m4. Unfortunately, the FSF lawyers have
been working on this issue for months now and it looks like it’s still going
to take some time. Some major tools (such as Autoconf 2.62) are being rolled
out with licenses clauses reverted to GPLv2+. I personally do not wish to do
that so what I’m going to do instead is to use the “beta” not-yet-official
exception clauses in boost.m4. This way those of you who want to use boost.m4
under other licenses (be it BSD or Boost licenses, or whatever), you’re free
(and welcome) to do so.