kicad-developers team mailing list archive

[hauptmech <hauptmech@xxxxxxxxx>]

I took a look at what approaches might work to fix this.

I looked at removing the RPATH manually, in keeping with manual file 
manipulation approach used by the authors of this section of the CMake 
file. Shell tools to do this don't appear to be universal and it's not 
using the CMake way. So I moved on.

The approach that looks the most promising to me is to create a second 
target for the scripting library with the same sources as pcbnew.kiface. 
Then CMakes install Target will remove the RPATH as expected. To reduce 
the impact on compile time one could use: 
https://cmake.org/Wiki/CMake/Tutorials/Object_Library

In the CMake file, Dick Hollenbeck mentions a future plan to use the 
pcbnew.kiface file directly. Not sure what was involved with that.

On 25/02/18 10:37, Carsten Schoenert wrote:
> Hello Wayne,
>
> Am 24.02.18 um 21:44 schrieb Wayne Stambaugh:
> > Carsten,
> >
> > On 02/24/2018 02:08 PM, Carsten Schoenert wrote:
> > > Hi,
> > >
> > > I guess it's not intended that the library / shared object _pcbnew.so
> > > build in pcbnew/ set up a RPATH based on the build directory?
> > This is the kicad python scripting shared object which should get
> > installed in the correct python library path.  CMake installs it in the
> > correct place on both my Debian and Ubuntu builds so I don't understand
> > what the issue is here.
> the build and installation is just fine, the issue is that this file has
> a RUNPATH set to folder there it was compiled. It should have *no* RUNPATH.