Yes. All the dependency relocation stuff is done in the install step. You can run kicad launcher directly from build folder… it will use the hardcoded path to *your* dependencies. So it will run on your machine but not on other ones. Also, from within the launcher pcbnew, etc. will work. The standalone binaries won’t run from build directory, because they won’t find the kiface dso’s… the load paths are hardcoded relative to the final main kicad.app bundle structure… which isn’t in place for the build folder of pcbnew, eeschema, etc.
Regards, Bernhard On 30.10.2014, at 18:42, Andy Peters <[email protected]> wrote: > >> On Oct 30, 2014, at 8:15 AM, Bernhard Stegmaier <[email protected]> >> wrote: >> >> You *must* do a “make install” and use that binaries/links (also, all the >> bundling/relocatong of libs is only done on the binaries created during >> install)… >> > > Slight swerve here, but ... I didn't realize that one needed to do a "make > install" after doing the main make on the kicad tree. So the "make install" > step is what bundles all of the static libraries properly? And when you use > the dmg-generator, it takes the results of the make install step, right? > > -a > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
