dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

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.

--
Anders


On Mon, Aug 09, 2010 at 04:26:29PM -0700, Johan Hake wrote:
> I think we definitely should generate a pkg-config file if it is possible, and
> install it in a given pkg-config path. pkg-config has nothing to do with
> SCons. If a pkg-config file is generated it will also be easier to be
> compatible with project using SCons together with pkg-config.
>
> That said, it is probably a good idea to also generate a .cmake file for
> DOLFIN which cmake-converts can use.
>
> Johan
>
> On Monday August 9 2010 15:40:42 Garth N. Wells wrote:
> > It seems that CMake requires less code than SCons, and it is much easier
> > to test for dependencies. What's the recommended approach to building
> > executables? Should a pkg-config file be created when building the
> > library or a .cmake file?
> >
> > Garth
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dolfin
> > Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dolfin
> > More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp

Attachment: signature.asc
Description: Digital signature