On Mon, Jan 20, 2014 at 12:09 PM, Nick Wellnhofer <[email protected]> wrote: > Now that we’re about to build Clownfish and Lucy separately, we have to find > a way to point Lucy to the Clownfish .cfh files. I can see the following > options: > > * Add a command-line option to Lucy’s build scripts which in > turn gets passed to the Clownfish compiler.
+1 > * Use an environment variable like CLOWNFISH_INCLUDE which > contains a list of paths the Clownfish compiler should search. +1 > * Install .cfh files in some well-known locations like > /usr/include/cfh, /usr/local/include/cfh and have CFC always > search there. 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. Marvin Humphrey
