← Back to team overview

kicad-developers team mailing list archive

Re: Eeschema relative file handling


This is by design due the myriad of issue we used to have depending on
the state current working directory.  The decision was made to use
absolute paths so if the cwd was abused by someone in the kicad source,
absolute file paths are guaranteed to work correctly.  Please do not
change it.



On 11/13/2017 9:43 PM, Jon Evans wrote:
> I noticed that when I run eeschema as a single binary rather than
> starting through the kicad shell, I cannot pass a relative filename as
> the argument (single_top.cpp passes the argument straight through
> to SCH_EDIT_FRAME::OpenProjectFiles(), which asserts when given a
> relative path).
> Is this behavior intentional?  If so, why?  I can see code in
> PGM_SINGLE_TOP::OnPgmInit() that converts the first argument to an
> absolute path, but only if there is more than one argument.  I'm not
> sure the history here, so not sure if this is a bug or desired behavior
> for some reason.
> Anyone opposed to me changing it so that I can pass a relative path to
> eeschema and have it work?
> -Jon
> _______________________________________________
> 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