kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #04577
Re: Library configuration
-
To:
kicad-devel@xxxxxxxxxxxxxxx
-
From:
Terry Barnaby <terry1@...>
-
Date:
Thu, 18 Mar 2010 12:27:16 +0000
-
Cc:
Terry Barnaby <terry1@...>,
-
In-reply-to:
<4BA15008.7050302@...>
-
User-agent:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
Ok, I think I have found the basic problem. I think it is a bug
in kicad, but I haven't tracked down the exact bit of code
that is causing the issue. (eeschema_config.cpp, projet_config.cpp ?)
I am an old Unix/Linux command line user and most of the time run
applications while in the working directory where the circuit design
is stored. If you do this and use relative paths for the *.pro file
then kicad does not actually read the file and eeschema uses its
template kicad.pro file with no errors or warnings.
So if you run something like "kicad CarHorn.pro" in the directory
where your design is kicad will not read the config file.
I suspect the lower level wxFileConfig class needs an absolute
path but kicad is just passing "CarHorn.pro".
Terry
Follow ups
References