kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

Hi Garth,

I agree 100%.  I can create a path to the included bundled help PDFs with a
relative path from the currently running executable.

If I was assuming they would be at /Applications/Kicad/Kicad.app I wouldn't
have to ask the program where it was running--I would just hardcode that :)

This is definitely the whole point of bundling everything together--but
both the Windows and Linux installs appear to put the help files in a known
location, rather than in a relocatable bundle along with the executables
like we're doing on OS X, so it wasn't as easy as just adding a third
location to the file.

Furthermore, I think I found a function call to get the path of the
currently running executable.  As soon as I get it working I'll send a
patch to the list.

Adam Wolf
Cofounder and Engineer
W&L

On Mon, Nov 17, 2014 at 10:32 PM, Garth Corral <gcorral@xxxxxxxxx> wrote:

> I’m not sure I understand what you mean.  The application bundle would be
> kicad.app.  Are you assuming that everyone will install the entire package
> directory in /Applications?  If so, you shouldn’t.  I, for one, only
> install the actual application bundle, kicad.app.  I thought that this was
> the point of Bernhard doing all the work of bundling everything, so that
> folks can simply do a drag and drop install of the application as is
> customary on OS X.  Assuming that I have a folder of stuff outside the
> bundle but in the applications folder breaks this.
>
>
> Garth
>
>
>
> On Nov 17, 2014, at 8:16 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
>
> Hi folks,
>
> I'm trying to wrap up the last few remaining bugs before I'm happy with
> the OS X package.
>
> One of them is to get the "Getting Started" and other help files to work.
> My current packages put the help PDFs in English in the application bundle,
> near the executables.  Due to OS X custom, these are *probably* at
> /Applications/Kicad/help/, but it is not safe to rely on that.  On the
> other hand, I can build a relative path from the current path of the
> executable, and be relatively confident there.
>
> I am looking at SearchHelpFileFullPath and I see two bases for the
> search--DEFAULT_INSTALL_PATH and the KICAD environment variable.
>
> Is there an easy way to get the path to the currently running executable
> in this file?
>
> I am definitely still learning my way around the code base...
>
> Thanks!
>
> Adam Wolf
> Cofounder and Engineer
> W&L
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>