kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #18234
Re: yet another search path list issue? (Maybe a Mac issue, or Mac build issue)
It used kicad.pro when launched from Kicad, but not from eeschema directly,
right?
On May 9, 2015 3:32 PM, "Bernhard Stegmaier" <stegmaier@xxxxxxxxxxxxx>
wrote:
> Hi,
>
> >> * If we have search paths, why do we include some libraries by default
> in
> >> the top pane?
> >
> > Good question, I have also been wondering about this. But I think
> > those are the explicit libs specified in the .pro template.
>
> Yes, it shows what is in the xxx.pro file.
> The xxx part is quite some magic I also don’t fully understand… I think
> normally it is equal to file name of the schematic or project.
> If nothing is given (start eeschema without anything standalone), then I
> guess it was supposed to use the kicad.pro template from the search paths.
> But, this was broken… just an empty file was used.
>
> That’s the issue I just sent a small patch for...
>
> >> * What determines what is in that top pane for new projects?
> >
> > I think the explicitly defined libs, which is saved in the pro file. (I
> think)
>
> With the patch I sent, the kicad.pro template from the search stack (on
> OS X this most likely will be the one from the app bundle) will be copied
> once to the preference folder and will be used from then on.
>
>
> Regards,
> Bernhard
>
>
Follow ups
References