[petsc-dev] buildsystem: cusp location

[Jed Brown]

On Sun, Mar 25, 2012 at 11:59, Satish Balay <balay at mcs.anl.gov> wrote:

> When configure is doing --download-cusp - it can determine how cusp is
> organized. [I think we try to place in PETSC_DIR/PETSC_ARCH/include.
> But since cusp decides how it installs itself [say user installs and
> installs manually] - we try to support that mode using
> --with-cusp-dir= option. There is no 'include/' dir in that mode of
> install.
>

Well isn't that what --with-cusp-include= is for?

I even wouldn't object to being lenient, but I don't think it makes sense
to abuse the meaning of --with-cusp-dir=.


>
> Yes - currently the situation is not ideal. The ideal situation is
> folks install cusp thrust - the recommended way - i.e along with cuda
> in cuda includes. One has to do this with thrust anyway - otherwise
> nvcc will always pick up thrust bundled with cuda - and now what you
> specify with -I/path-to-thrust.
>
> The other problem currently with cusp/thrust is - we've been using dev
> snapshot of cusp/thrust for a while. I don't know if there is a
> release snapshot of these packages that we can switch to now [or not].
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120325/3f4d02c6/attachment.html>