[MOAB-dev] Problems with MOABConfig.cmake
Vijay S. Mahadevan
vijay.m at gmail.com
Sat Nov 29 09:04:19 CST 2014
Thanks for the bug report John. We will push a fix to the MOABConfig
generation.
We can split the directory and library as separate variables but this
follows the autoconf based moab.make that uses the mixed convention. Is
there a specific reason why you want them separately? Apps using MOAB
should directly use that line to link anyway.
Vijay
On Nov 28, 2014 11:05 PM, "JR Cary" <cary at txcorp.com> wrote:
> Dear moab folks,
>
> I just configure moab with
>
> '/Users/cary/projects/dagmcall/moab/configure'
> --prefix=/volatile/moab-master.r5237-sersh --disable-static --enable-shared
> CC='/usr/bin/clang' CXX='/usr/bin/clang++' FC='/usr/local/bin/gfortran'
> F77='/usr/local/bin/gfortran' CXXFLAGS='-stdlib=libstdc++' FFLAGS='-pipe
> -fPIC' FCFLAGS='-pipe -fPIC' --enable-dagmc --without-vtk
> --with-hdf5='/contrib/hdf5-1.8.13-sersh'
>
> on Darwin. It built and installed, but at the end of the cmake
> configuration file (lib/MOABConfig.cmake) I see many lines beginning
> with '-n' and then 'n' at line endings:
>
> # Library and include defs
> SET(MOAB_INCLUDE_DIRS "/volatile/moab-master.r5237-sersh/include")
> -n SET(MOAB_LIBRARIES "
> -n -L/contrib/hdf5-1.8.13-sersh/lib
> -L/volatile/moab-master.r5237-sersh/lib -lMOAB -lc++ -lpthread -lz -ldl
> -lm -lhdf5")n
> -n SET(DAGMC_LIBRARIES "
> -n -L/contrib/hdf5-1.8.13-sersh/lib
> -L/volatile/moab-master.r5237-sersh/lib -ldagmc -lMOAB -lc++ -lpthread -lz
> -ldl -lm -lhdf5")n
>
> This causes any cmake project depending on moab to fail.
>
> It is also a bit strange, in that in cmake-land, libraries are what
> is after the -l, and LIBRARY_DIRS are what is after the -L.
>
> ......John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20141129/738fe025/attachment.html>
More information about the moab-dev
mailing list