dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #18973
Re: CMake
On Tue, Aug 10, 2010 at 09:26:06AM +0100, Garth N. Wells wrote:
> On Tue, 2010-08-10 at 09:47 +0200, Anders Logg wrote:
> > Maybe a .cmake file will be useful, but I think the first option
> > should be to (1) generate a pkg-config file and (2) use simple
> > Makefiles for all the demos.
> >
>
> A .cmake file is probably a bit more than just useful if we want to take
> advantage of the cross-platform features of CMake.
ok.
> An awkwardness with pkg-config + CMake is that we need a FindFoo.cmake
> file for each dependency, then we also need to create a pkg-config for
> each dependency, both of which do more or less the same thing. We
> created pkg-config files with SCons, so hopefully this is just as easy
> with CMake.
Do we really need to create pkg-config files for all dependencies? It
should be enough for us to provide the flags for how to build against
DOLFIN (which in turn is linked against its dependendices).
The reason for creating pkg-config files before was that the Scons
build system relied on pkg-config files. We looked for dependencies
and wrote down the information to pkg-config files, then read it back
in again during build.
--
Anders
Attachment:
signature.asc
Description: Digital signature
Follow ups
References
-
CMake
From: Garth N. Wells, 2010-08-09
-
Re: CMake
From: Johan Hake, 2010-08-09
-
Re: CMake
From: Anders Logg, 2010-08-10
-
Re: CMake
From: Garth N. Wells, 2010-08-10