lib.version is only expanded if the file named by $(metafile) exists, but then it uses a hardcoded filename to do the actual expansion.

this patch uses $(metafile) to do the expansion instead.

use $(metafile) instead of hardcoded filename in lib.version expansion

This commit reorganizes the accumulation of build flags in such a way that
non-obligatory build flags can be overriden or added by specifying
CPPFLAGS, CFLAGS and LDFLAGS as arguments from command line or environment.

I've also tried to make printed info a bit more helpful.

Targets pre and post can be defined in the including (library) makefile.
They are added to provide extra flexibility. Target all will
build pre, $(executable) and post in deterministic order. Built-in
documentation is modified to reflect the new situation.

This merge introduces the evaluation of optional multiline defines
'forLinux', 'forDarwin' and 'forWindows', which can be used as a flexible
replacement for system-specific variables as in Pd-extended's Makefile
template. Example code is added to Makefile.pdlibbuilder's built-in
documentation.

Command line variable CFLAGS now work according to conventions (overriding
all non-essential C flags). CPPFLAGS and LDFLAGS are also implemented.
Built-in documentation updated.

Phony target 'pre' forces rebuilds. This should not be default
behavior of Makefile.pdlibbuilder. If one needs a pre-build target
(phony or real file), declare it as prerequisite of $(all.objects)
in the library makefile after inclusion of Makefile.pdlibbuilder.
A pre-build target can have any name that isn't a target in
Makefile.pdlibbuilder.

Also remove associated documentation comments.

Multiple arch flags are incompatible with option -MM for preprocessor
on (at least) OSX <= 10.5. Non clean builds would stall on this. This
commit disables dependency checking for fat builds (current default
for OSX) on ppc and i386. Assuming that development is done on newer
systems / machines it should rarely hurt.

The bug was probably introduced with version 0.2.3.
Bump version to 0.2.4.

And bump version to 0.2.5

...like '$' (e.g. "$arg-help.pd")
by installing them one-by-one and using single-quotes
(so the shell doesn't expand the dollargs)

NOTE: this does not fix compiling such weirdo filenames

Closes: pure-data/pd-lib-builder#19

Only pass flags categories which can be expected to hold -I flags
to the preprocessor for dependency checking. Omit categories which
may contain architecture and tuning flags. This is a small and
hopefully reasonable limitation of dependency-checking functionality.
The preprocessor will still see predefined macros, amongst which
architecture definition. Thus, eventual architecture-dependent include
statements in the source code are considered for native architecture
during dependency checking.

This commit should resolve the rebuild issue on OSX, where some compiler
versions can not handle multiple architecture flags during dependency
checking.

Multiple defaults cause confusion and after discussion vanilla is preferred
default because:

1. vanilla is actively maintained
2. currently most pd lib authors develop against vanilla
3. unlike other pd flavors, vanilla is not part of a centralized build system
   with internal include path

Makefile.pdlibbuilder sets a default minimum OSX version for optimal
support of older OSX versions. With this commit, '-mmacosx-version-min=*'
in variable 'cflags' from the lib makefile is respected, not overridden.

A lib makefile can now determine the minimum OSX version (for example to
support C++11, which was the direct motivation for this change).

This is a response to pull request #22 'Making minimum Mac OS X version
configurable', but note that it is implemented in a different way.

Update version number because of previous (merge) commit. The
merge was done with github's 'Merge' button. Never again. The merged
commit was 49a0b2f from 2016-06-28 allowing installed files to
contain weirdo characters, and closing issue #19.

This variable is useful when building against a 'portable' pd install.
Makefile.pdlibbuilder should now be compatible with centralized build
systems when PD_PATH is passed as make argument, or set in environment.

The issue was introduced in version 0.3.0 from the previous commit
(41e9743).

These new path variables are aliases of existing ones that didn't have
coherent names. The new variables are all defined such that they are
overridable from the environment, as indicated by the upper case syntax.

Variables PDDIR, PDINCLUDEDIR, PDBINDIR and PDLIBDIR were introduced in
the previous commit as API replacement for a less coherent set of path
variable names, and made these paths settable in the environment.
This commit (re)writes variable descriptions accordingly and reorganizes
descriptions with the intention to give a more comprehensible overview of
the API structure.

This merges commit a7d3098 which responded to issue #22. With this commit,
cflag '-mmacosx-version-min=*' from a lib makefile is respected, not
overridden by a default minimum version.

And bump to version 0.4.2

Reportedly '-fPIC' should work for all architectures while '-fpic'
does not.

This evaluates correctly in the case where 'system' is defined for
the purpose of cross compiling. This commit addresses issue #31.

This is in preparation for target architecture detection through
gcc / g++.

It stores the first field of <cpu>-<vendor>-<os> triplet
as retrieved from command '<compiler> -dumpmachine' where <compiler>
is g++ or gcc.

As per suggestion of Johannes Zmoelnig. It is not relevant and
also not compatible with x86_64.

And explicitly specify Intel 32 bit architectures, where 'mingw32'
is included to support MSYS1.

Needed for building with pd-lib-builder on AppVeyor.

Long option name '--machine' was introduced in commit fa3c2ca for
explicitness, however it is not supported by clang / OSX.

This merges a series of commits implementing target
architecture detection for Windows builds, and the
setting of appropriate options for 32 and 64 bit builds.

Update version number after merge commit 215bf3e. This is the first
version handling 64 bit builds for Windows.

…851b30'

git-subtree-dir: pd-lib-builder
git-subtree-mainline: 81d22e6
git-subtree-split: 7d4c0ca9bb184acfde98469f1ba9670f8f851b30

On MacOS there is no libpocketsphinx.so only  libpocketsphinx.dylib

was getting "ERROR: "ngrams_raw.c", line 356: Corrupted model, some trigrams have no corresponding bigram" because old models were corrupted (see https://stackoverflow.com/questions/36409042/pocketsphinx-error-reading-hub4-5000-dmp"

replace old models (corrupted) with new ones

homebrew installs sphinx stuff in weird places so i recomend just downloading from github, make and install oneself