Re: [Paraview] Using ninja to build/install ParaView

2018-04-04 Thread David E DeMarle 
I agree with Mathieu, you don't need a fork of Ninja to build/install
paraview.

Chris you might be interested in the paraview superbuild project -
https://gitlab.kitware.com/paraview/paraview-superbuild

We use that to 1) make our redistributable binaries and 2) to deploy
paraview on clusters and supercomputers. Two salient features in it are
that 1) it can either build and package or or simply use system versions of
paraview's dependencies, and 2) that it fixes up the library paths when
needed.

hth




David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Wed, Apr 4, 2018 at 1:43 AM, Mathieu Westphal <
mathieu.westp...@kitware.com> wrote:

> Hi Chris,
>
> AFAIK, ParaView does not require the kitware fork of Ninja.
> I just build and installed with Ninja 1.8.2, it works well and the
> installed binaries links correctly.
>
> Could you check with a standard Ninja ? and could you precise your
> configuration options ?
>
> Best,
>
> Mathieu Westphal
>
> On Tue, Apr 3, 2018 at 10:50 PM, Chris Coutinho 
> wrote:
>
>> 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 –  5785
>>
>> post: Postbox 199, 8600 AD Sneek
>>
>> bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek
>>
>> email: c.couti...@redstack.nl
>>
>> www: www.redstack.nl
>>
>>
>>
>> [image: REDstack_logo2]
>>
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Using ninja to build/install ParaView

2018-04-03 Thread Mathieu Westphal 
Hi Chris,

AFAIK, ParaView does not require the kitware fork of Ninja.
I just build and installed with Ninja 1.8.2, it works well and the
installed binaries links correctly.

Could you check with a standard Ninja ? and could you precise your
configuration options ?

Best,

Mathieu Westphal

On Tue, Apr 3, 2018 at 10:50 PM, Chris Coutinho 
wrote:

> 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 –  5785
>
> post: Postbox 199, 8600 AD Sneek
>
> bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek
>
> email: c.couti...@redstack.nl
>
> www: www.redstack.nl
>
>
>
> [image: REDstack_logo2]
>
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

[Paraview] Using ninja to build/install ParaView

2018-04-03 Thread 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 –  5785

post: Postbox 199, 8600 AD Sneek

bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek

email: c.couti...@redstack.nl  

www: www.redstack.nl  

 



 


pgpoabVXRz_Eu.pgp
Description: PGP signature
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview