cvpcb bzr4555 - doesn't see fp library when started from launcher

[madworm]

If cvpcb is started from within eeschema, it sees all the footprint libraries that are in "fp_lib_table" of a project. Works as expected.

If it is started using the kicad launcher, the netlist is loaded, but the "project specific libraries" are empty. Trying to add those libraries doesn't seem to work. They show up, but are "empty". It behaves quite weirdly.

---

Application: CvPcb
Version: (2013-12-14 BZR 4555)-product Release build
wxWidgets: Version 2.8.12 (release,Unicode,compiler with C++ ABI 1002,GCC 4.8.1,STL containers,compatible with 2.6)
Platform: Linux 3.11.6-4-desktop x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.54.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=OFF
         KICAD_SCRIPTING_MODULES=OFF
         KICAD_SCRIPTING_WXPYTHON=OFF
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=OFF

[Wayne Stambaugh (stambaughw)]

On 12/17/2013 3:39 PM, madworm wrote:
> Public bug reported:
>
> If cvpcb is started from within eeschema, it sees all the footprint
> libraries that are in "fp_lib_table" of a project. Works as expected.
>
> If it is started using the kicad launcher, the netlist is loaded, but
> the "project specific libraries" are empty. Trying to add those
> libraries doesn't seem to work. They show up, but are "empty". It
> behaves quite weirdly.

CvPcb (or Pcbnew for that matter) does not automatically add project
specific footprint libraries to the table. It has no way of knowing
which libraries from the legacy library list are project specific and it
doesn't know how you want to define the URL so you must add them
manually to the table. I did confirm that adding a new library (project
or global) to the table fails to load the footprints. This happens no
matter how CvPcb is launched. If you you close CvPcb and reopen it, the
footprints will be loaded correctly. I'll fix the new table entry
loading bug.

>
> ---
>
> Application: CvPcb
> Version: (2013-12-14 BZR 4555)-product Release build
> wxWidgets: Version 2.8.12 (release,Unicode,compiler with C++ ABI 1002,GCC 4.8.1,STL containers,compatible with 2.6)
> Platform: Linux 3.11.6-4-desktop x86_64, 64 bit, Little endian, wxGTK
> Boost version: 1.54.0
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=OFF
> KICAD_SCRIPTING_MODULES=OFF
> KICAD_SCRIPTING_WXPYTHON=OFF
> USE_FP_LIB_TABLE=HARD_CODED_ON
> BUILD_GITHUB_PLUGIN=OFF
>
> ** Affects: kicad
> Importance: Undecided
> Status: New
>

[madworm (madworm-de-inkscape)]

Maybe I should be a bit more specific.

I have an existing project. The footprint libraries were added within pcbnew. fp_lib... is populated.

Starting cvpcb via the launcher doesn't work (as previously described), starting it from within eeschema works. Starting cvpcb via console and loading the netlist manually works as well.

[Wayne Stambaugh (stambaughw)]

I could not duplicate this bug. Here are the steps I took.

1. Open an existing project in KiCad.
2. Launch Pcbnew from KiCad.
3. Add entries to project footprint library table in Pcbnew.
4. Launch CvPcb from KiCad (Pcbnew is still open).

The table entries added in Pcbnew are showing up correctly in CvPcb. Is there an fp-lib-table file in your project folder? If not, maybe there is a difference between Windows and Linux. I'll verify when I get a chance. If there is a valid fp-lib-table file in your project folder, than I am a loss as to why you are seeing this issue.

[madworm (madworm-de-inkscape)]

Yes, that is what I do as well.

There are 2 fp-lib-table files: one in my home-folder (which should really be in .kicad/) and the other one is in the project folder.

I've played a bit with the "file-audit" daemon and found the following:

1) if cvpcb is started from within eeschema BOTH fp-lib-table files are accessed and opened by it (expected behaviour).

2) if cvpcb is started by the launcher, only the global fp-lib-table files is accessed and opened (which is empty).

As the project-specific fp-lib-table file is never accessed in case 2), it is no wonder why I don't see any footprints.