Re: [petsc-dev] buildsystem: cusp location
On Sun, Mar 25, 2012 at 4:53 PM, Satish Balay <[email protected]> wrote:
On Sun, 25 Mar 2012, Jed Brown wrote:
On Sun, Mar 25, 2012 at 16:32, Matthew Knepley <[email protected]> wrote:
Isn't the final point here that we are trying to let the user do the dumbest, easiest thing? Maybe no Linux distribution does this, but we are trying to cope with bad input from a user not using a nice distro.
The price we would pay for cleaning up our internals is demanding that users think more about the configure input. This is not always a good tradeoff.
Simple compromise proposal:
--with-cusp-dir=/prefix
Looks in /prefix/include/ for the headers <cusp/version.h>. If unsuccessful, it tries /prefix/.
Ok - for my part I've already agreed to this. [sean proposal (1)?]
BuildSystem has a way of looping over libdir/libname options. Don't know if it can currently do the same for includes. [Hence my initial attempt to support cusp/thrust was to do a replace of the default choice - instead of trying them all]
Yes you can put different include options in the generator in the same way. Matt
Satish
If you insisted, it could even search in the other order. What I don't
like
is --with-cusp-dir=/prefix not looking for headers in /prefix/include/.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
participants (1)
-
Matthew Knepley