Hi, On Sunday, June 22, 2014 20:28:00 Joakim Hove wrote: > I think we all agree that OPM is (and in my opinions should remain) more on > libraries and core functionality, and less on end user applications. But if > that strategy is to credible it must be simple for third party developers > like Paolo to build applications on top of the opm libraries – that is > currently not the case.
I agree: IMHO this is a call for a shell script which allows to easily create
a bare-bones module (DUNE has a script called 'duneproject' for this purpose,
but I do not know how reliable it is) and for either moving the build system
into a separate module or making it distributed over the modules (the second
option is the path taken by DUNE). Replicating everything to all modules is
clearly unfeasible because, even though build system changes can be propagated
to all "official" modules, external ones need to be left standing in the rain.
That said, if there are no miracles, this can only be done for the next-after-
next release at the earliest (i.e., next year). IMHO this should be also used
as an opportunity to refurbish the division of functionality between the
modules...
> To be honest I think I would have had to resort to
> Andreas suggestion myself – is this the time when I *really* should
> understand how pkg-config works?
AFAICS pkg-config does not help too much here: it makes it easier to write
cmake/autoconf modules because it provides a (relatively) simple canonical way
to retrieve the relevant compiler and linker flags, but it does not allow to
get rid of the need to write such tests in the first place. I like to think of
it as a non-cmake specific way of detecting the settings required for packages.
(note that it trades "non-cmake specific" for "only available on UNIXoid
systems".)
cheers
Andreas
--
Notice: "String" and "Thread" are the same thing to non-computing
people.
— Programming.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
