kicad-developers team mailing list archive

[Nathan McCorkle <nmz787@xxxxxxxxx>]

On Wed, Sep 3, 2014 at 12:27 PM, Lorenzo Marcantonio
<l.marcantonio@xxxxxxxxxxxx> wrote:
> It's true that you *could* set all these paths in a config file (and
> wouldn't be a bad idea, either). But at the end you'll need something
> like KICAD_CONFIG (defaulted to something like
> $HOME/.config/kicad/env-config) to supply the path of the config file to
> use

I don't follow your logic... why would you still need a KICAD_CONFIG
env-var? Why wouldn't that file come in the cloned repo with defaults
populated, and sit next to the executables or shared-libs (so the path
is constant, or constant relative to some file which is constant)? I
just compiled yesterday and that build was using all sorts of things
relating to a previously installed build.... totally breaking the
testing I wanted to do.


-- 
-Nathan