With 2014-09-19 BZR 5142's eeschema, How do I get back parts in /usr/local/share/kicad/libs?

Asked by Joseph Chen

Before updating to 2014-09-19 BZR 5142, I had no problems at all to use eeschema to place any parts under "/usr/local/share/kicad/libs". But now, the "place" command only see parts in "power" plus ones in my own chace.

Do I need to configure anything else to make it work again with this new version?

FYI, I used "kicad-install.sh --install-or-update" to update and compile KiCad in my Ubuntu 14.04.

--Joe

Question information

Language:
English Edit question
Status:
Solved
For:
KiCad Edit question
Assignee:
No assignee Edit question
Solved by:
Joseph Chen
Solved:
Last query:
Last reply:
Revision history for this message
Wayne Stambaugh (stambaughw) said :
#1

For future reference, please do not file a bug report and then ask a question on the same topic here. Your question is a user question not a development question. This is the development site. User questions should be asked on the KiCad users group at https://groups.yahoo.com/neo/groups/kicad-users/info. Before you file another bug report, please read https://answers.launchpad.net/kicad/+faq/1108.

In the schematic editor, open the library management dialog in the Preferences->Set Active Libraries menu entry. If the path /user/local/share/kicad/libs is not in the "Current search path list", then you must add it to the "User defined search path" list assuming that is where you component libraries are actually installed. There have been some changes to the way library search paths are handled made to KiCad so that may be the problem you are experiencing.

Revision history for this message
Joseph Chen (joseph-chen59) said :
#2

Wayne,

Thanks for the reminding and reply. I will remove the bug report and keep this question entry.

The problem remains even though the library path setting is correctly set by default.

My Eeschema's libray path setting looks correct and the entry of "/usr/local/share/kicad/library" has been there all the time inside the "Current search path list".

I also tried with adding a redundent entry in the "User defined search path" but to no avail.

Revision history for this message
Joseph Chen (joseph-chen59) said :
#3

Can't figure out to delete the duplicated bug report on this issue.

Try to use "Line existing bug" and hopefully it works for.

 My appologies.

Revision history for this message
Wayne Stambaugh (stambaughw) said :
#4

The only thing I can think of is your libraries are not in that path or you do not have permission to read them. You did confirm that the libraries are in /usr/local/share/kicad/library didn't you?

Revision history for this message
Joseph Chen (joseph-chen59) said :
#5

I think I found the ROOT cause of the disappeared eeschama libraries with the BZR 5142 and later versions.

It's the COMPATIBITY of the old "*.pro" and new "*.pro" files.

In the new "*.pro" files, there is an automatically added entry of [eeschema/libraries], under which all the library names are explicitly inserted, or duplicated. In contrast, the old "*.pro" files (I have a few such files that were started about a half year ago.) have NONE of it, and they were working fine with eeschema util I tried with BZR 1542 version.

 In short, the NEW eeschema generates, or duplicates, the common library names of "/usr/local/share/kicad/library" within a individual project file "*.pro", if they are started anew, while with existing "*pro" files, eeschema does nothing, and fails to find any libraries, despite the "current search path list" contains all the library paths correctly.

I am sure someone else who like me started the designs a while ago WILL encounter the same problem.

In my personal opinion, I prefer the old eeschema behavior of not duplicating the common library names in individual project files.

Revision history for this message
Joseph Chen (joseph-chen59) said :
#6

Some more findings...

I suspect my existing "*.pro" file was stripped off the [eeschema/libraries] somehow when was saved with the new version eeschema. Could this be possible?

I found out this when I noticed my "*.pro" files was modified. After reversing the unwanted modifications eeschema starts get the part libraris correctly.

Revision history for this message
Joseph Chen (joseph-chen59) said :
#7

No loger an issue with newer version.