On 21/01/2014 17:44, Marvin Humphrey wrote:
I would tweak this to be specific per host. Multiple, incompatible versions
of Clownfish must be allowed to co-exist simultaneously on a given system, so
that it is possible to upgrade them independently. That means that the
Clownfish which is installed with e.g. Python 3.3 should look here first:
$PYTHON_INSTALL/include/python3.3m/cfh
I think the paths that you specify above make sense for the C Clownfish
host bindings. I'm not sure that Clownfish installed with other hosts should
look there at all, though -- it seems like asking for trouble. For example,
a Python Clownfish might find header files for a library in
/usr/local/include/cfh which does not have Python bindings installed.
Yes, these paths should only be used for the C bindings. Thinking more about
it, $PREFIX/share/clownfish/include would be a better place.
We already worked out a path for Perl. See sub cf_system_include_dirs in
Clownfish::CFC::Perl::Build. It currently searches
$installsitearch/Clownfish/_include
$installvendorarch/Clownfish/_include
Nick
