On Wed, 15 Jan 2014 14:20:08 +0100 Jan Blechta <[email protected]> wrote:
> On Tue, 14 Jan 2014 17:42:42 +0100 > Johannes Ring <[email protected]> wrote: > > > On Tue, Jan 14, 2014 at 5:06 PM, Jan Blechta > > <[email protected]> wrote: > > > Is there a way choosing a SWIG installation if there are multiple > > > of them on the system? It seems that CMake-built-in FindSWIG, say > > > > > > $CMAKE_ROOT/share/cmake-2.8/Modules/FindSWIG.cmake > > > > > > picks one regardless of preset values SWIG_DIR and > > > SWIG_EXECUTABLE. > > > > You should be able to force this by running cmake with > > -DSWIG_EXECUTABLE:FILEPATH=/path/to/swig. Doesn't that work for you? > > Ok, this works. But generated code uses wrong swig version and > ffc/jitcompiler.py:check_swig_version(compiled_module) raises. > > I guess that possible reason is that one my SWIGs has both swig2.0 and > swig executables while another has only swig. FindSWIG.cmake prefers > swig2.0 executable. So can -DSWIG_EXECUTABLE be passed to cmake when > configuring an extension module? Oh yes, making a symlink swig2.0 -> swig fixes the problem. Jan > > Jan > > > > > Johannes > > _______________________________________________ > > fenics-support mailing list > > [email protected] > > http://fenicsproject.org/mailman/listinfo/fenics-support > > _______________________________________________ > fenics-support mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics-support _______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
