← Back to team overview

kicad-developers team mailing list archive

Re: Getting libraries when building from source.

 

I might have read your original mail a bit wrong, the dickelbeck lib is the
legacy one.

But it should be enough with only the github plugin AFIK, you can verify it
by looking at the Help menu and then the version information. If you want
to use online pretty libs you also need to make sure that the KIGITHUB env
variable is set.


2014-02-17 20:22 GMT+01:00 Sean Silva <chisophugis@xxxxxxxxx>:

>
>
>
> On Mon, Feb 17, 2014 at 2:20 PM, Carl Poirier <carl.poirier.2@xxxxxxxxx>wrote:
>
>> Have you built KiCad with the GitHub plugin enabled?
>>
>
> My CMakeCache says:
> //Build the GITHUB_PLUGIN for pcbnew.
> BUILD_GITHUB_PLUGIN:BOOL=ON
>
> so I assume yes. Is there anything else I need to do to enable it?
>
> -- Sean Silva
>
>
>>
>>
>> On Sun, Feb 16, 2014 at 11:01 AM, Sean Silva <chisophugis@xxxxxxxxx>wrote:
>>
>>>
>>>
>>>
>>> On Sun, Feb 16, 2014 at 9:01 AM, Nick Østergaard <oe.nick@xxxxxxxxx>wrote:
>>>
>>>> See https://lists.launchpad.net/kicad-lib-committers/msg00034.html
>>>>
>>>> Which means that you should basically checkout
>>>> lp:~dickelbeck/kicad/library-read-only instead. I guess the information
>>>> should be updated on the website also, by those who have write access.
>>>>
>>>
>>> Thanks for the information. I followed the same steps as on the wiki,
>>> except using lp:~dickelbeck/kicad/library-read-only instead, but I'm still
>>> running into the same issue. In particular, when I open up cvpcb, there are
>>> no footprints available.
>>>
>>> I'm getting errors like "Cannot find footprint library file
>>> 'sockets.mod' in any of the KiCad legacy library search paths.". There is
>>> no file sockets.mod, but there is a file Sockets.mod present in
>>> $INSTALL_ROOT/share/kicad/modules/. I tried renaming the file to
>>> sockets.mod but that doesn't seem to make any difference (no footprints
>>> appear either way).
>>>
>>> It seems like there is a lot of mention of "legacy" in the dialogs when
>>> using this approach. Is there a different approach that I should be using
>>> which is non-"legacy"?
>>>
>>> -- Sean Silva
>>>
>>>
>>>>
>>>> 2014-02-16 1:54 GMT+01:00 Sean Silva <chisophugis@xxxxxxxxx>:
>>>>
>>>>>  Is there a preferred way to do this? Just building lp:kicad there
>>>>> doesn't seem to be any library stuff included. What I was able to find was:
>>>>>
>>>>> There seems to be <https://github.com/KiCad/kicad-library> and all
>>>>> the *.pretty repos on github, but I wasn't able to find an explanation of
>>>>> how to integrate that into the basic source build/install.
>>>>>
>>>>> Also, at the bottom of <
>>>>> http://www.kicad-pcb.org/display/DEV/Building+KiCad+on+Linux>, it
>>>>> says "If you want to also install the KiCad components library, you can use
>>>>> these commands:", but those commands don't work for me, and seem to be
>>>>> unrelated to the github libraries.
>>>>>
>>>>> So what is the usual/preferred way to get the libraries?
>>>>>
>>>>> -- Sean Silva
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>

Follow ups

References