kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

There's a kicad.app directory.  Next to that are the subapplication .app
directories, that cannot be moved relative to kicad.app, due to symlinks.
This is how it is today, and I'm not changing that.

The way I have set it up in the build server is that there is a help/
directory along side kicad.app and eeschema.app et al.  Inside of that
directory is the normal, KiCad help search path, so you could have an en/
directory, or an fr/ directory, or none, which opens the "default" docs.

If you don't store your help files there--that's ok.  You won't be any
worse off than you are today!

I have a patch coming in the next email that sets this up, but I want to
move the discussion from "How can I get access to the current executing
bundle" to "Here is a proposed patch that works with what I have set up on
the build server, let's discuss if there are any issues."

This setup accommodates the default OS X installation workflow, which is
that there is a .dmg with a single "thing" and a symlink to /Applications,
and users can drag the "thing" (.app or directory) into Applications, or
wherever they want, and it should still work.  I have posted previews of
these to the dev list already.

This workflow is going to be extended shortly, so there are two groups of
things--the Kicad/ directory containing kicad.app and eeschema.app et al,
which goes into /Applications (or wherever you want, but these packages are
aimed at typical Mac users, not developers), and Libraries, which goes into
where we already decided libraries will go on OS X.  I will be setting up a
pretty background to guide the user when I pull this in.

Adam Wolf
Cofounder and Engineer
W&L