Re: [ice-dev] VisIt Mac fix

["Perez, Danielle M" <danielle.perez@xxxxxxx>]

Could the DYLD library path for visit be done automatically when ice is fired up? That way we don't have to mess with our bash profiles or manually set it ourselves each time we use it. 

On Thu, May 7, 2015 at 4:52 PM, Harinarayan Krishnan <hkrishnan@xxxxxxx> wrote:

A minor add on would be to add ICE e after. 

To recap:

example script called 

ice.sh

#!bin/bash

set <DYLD_PATH>

run ICE. (visit should pick up the DYLD_LIBRARY_PATH of the parent (ICE) process.

This might be a quick thing to try.

Best regards,

Hari

On Thu, May 7, 2015 at 3:31 PM, Harinarayan Krishnan <hkrishnan@xxxxxxx> wrote:

There is a potential quick and easy workaround for this. One could simply create a "visit-ice" executable. That simply consists of

-----

#!/bin/bash

DYLD_LIBRARY_PATH=<VisIt-Path>:$DYLD_LIBRARY_PATH

<execute-visit>

-----

Finally, just call the visit-ice executable.

This way the environment doesn't get corrupted and ParaView still works.

Does this sound okay? or is VisIt and ParaView running under the same environment?

Best regards,

Hari

On Thu, May 7, 2015 at 3:03 PM, McCaskey, Alex <mccaskeyaj@xxxxxxxx> wrote:

Hey Hari, 

The current problem exists on Macs that have other VTK libraries in their DYLD_LIBRARY_PATH. I’m attaching a pdf explaining it and the current work-around I used. But turns out, this work-around might also affect some users Paraview installation. 

Alex

_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev

--

Danielle

"Look for a way to lift someone up. If that's all you do, it's enough."

-- Elizabeth Lesser

___________________

Danielle Perez

Nuclear Engineer

Fuel Modeling and Simulation

Idaho National Laboratory

P.O. Box 1625 MS 3840

Idaho Falls, ID 83415

Office: 208.526.1228

Cell: 208.520.8215

danielle.perez@xxxxxxx