SNL: Bad path in linking commands on Mac
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
This applies to a cvs checkout.
I discovered this bug because my own personal script for launching paraview kept disappearing. I have paraview built in ~/util/src/ParaView-datestring-build. I have a script in ~/util/bin that launches a particular build of paraview. When I build a new paraview, my script disappeared.
I've tracked it down to the linking command. The actual link command cds into GUI/Client and then builds the executable at ../../bin. Before the link command executes, the previous binary is removed. But it uses the same path without cd'ing first and ends up trying delete the binary somewhere outside of the build directory. Yikes! And hence, my poor little script which happens to be at ../../bin gets killed.
This problem showed up between 5/4 and 6/23.
Below are the linking commands.
Linking CXX executable ../../bin/paraview /Users/wkoegle/util/bin/cmake -E remove -f ../../bin/paraview cd /Users/wkoegle/util/src/ParaView/GUI/Client && c++ -Wno-deprecated -noprebind -g -fPIC "CMakeFiles/paraview.dir/ParaView.o" -o ../../bin/paraview -L