You can also check the structure of kicad.app in the bin folder.
This should be the *only* real app bundle, everything else must be a symbolic
link to inside kicad.app.
The overall kicad.app structure should be like that (from memory…):
kicad.app/
Contents/
Applications/
eeschema.app/
Contents/
MacOS/
eeschema/
Frameworks -> Symlink to kicad.app/Contents/Frameworks
pcbnew.app/
… similar to eeschema.app …
…
Frameworks/
… all the *.dylib
PlugIns/
eeschema.kiface
pcbnew.kiface
SharedSupport
… some other stuff …
At the same directory level as kicad.app pcbnew.app (and others) should be a
symlink to “kicad.app/Contents/Applications/pcbnew.app”.
You could also try to open kicad.app via right-click and “Show Package
Contents”, navigate to Contens/Applications folder and start pcbnew from there.
Regards,
Bernhard
On 30.10.2014, at 20:31, Adam Wolf <[email protected]> wrote:
> First, I'm going to grab the files from the bin/ directory, and compare them
> with the ones in the dmg, just to be sure. Then I'll put the DMG on Dropbox
> along with the build log.
>
> Adam Wolf
> Cofounder and Engineer
> W&L
>
> On Thu, Oct 30, 2014 at 2:23 PM, Bernhard Stegmaier <[email protected]>
> wrote:
> Can you put the build somewhere?
> I would like to try it… maybe I can see something being wrong?
>
>
> Regards,
> Bernhard
>
> On 30.10.2014, at 20:16, Adam Wolf <[email protected]> wrote:
>
>> In my build of 5236, after doing make install and running from the installed
>> location, I can start PCBNew from Kicad.app but not from PCBNew.app.
>>
>> Does this tell us anything about what went wrong?
>>
>> Adam Wolf
>>
>> On Thu, Oct 30, 2014 at 1:57 PM, Bernhard Stegmaier
>> <[email protected]> wrote:
>> 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
>>
>
>
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
