[Paraview] Using ninja to build/install ParaView

[Chris Coutinho]

Hello,

 

I’m using the Kitware fork of ninja, which builds the latest release candidate of ParaView just fine, but when I install it to the specified install location (via ninja install), all of the executables are suddenly unable to find other linked libraries. In the build directory everything works, but the locations of various libraries (ie MPI) don’t carry over, and calling ParaView fails due to not being able to find those libraries.

 

Running ‘ldd’ on the executable shows that that all the libraries aren’t able to be found.

 

I’m curious if this is just a fact of Ninja as primarily a dev tool, or maybe I’m just not passing it the proper flags?

 

 

Met vriendlijke groet,

REDstack BV

 

Chris Coutinho

Onderzoeker/Data Analist

 

tel: +31 (0)6 – 2222 5785

post: Postbox 199, 8600 AD Sneek

bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek

email: c.coutinho at redstack.nl <mailto:c.coutinho at redstack.nl> 

www: www.redstack.nl <http://www.redstack.nl/> 

 



 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180403/75b3be38/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 39396 bytes
Desc: not available
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180403/75b3be38/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180403/75b3be38/attachment.sig>