Not sure if fixed.
I can see the project-specific path correctly both times, which is good.
There is still a difference somewhere in that the ~/prj-fp-lib-table is read when invoking cvpcb from the toplevel, while this does not happen when invoked from eeschema.
I have a (nonsensical) table in my homedir:
$ cat ~/prj-fp-lib-table (fp_lib_table (lib (name foo)(type KiCad)(uri bar)(options "")(descr "")) )
and I get an error dialog for this only when opening a .net file.
Not sure if fixed.
I can see the project-specific path correctly both times, which is good.
There is still a difference somewhere in that the ~/prj-fp-lib-table is read when invoking cvpcb from the toplevel, while this does not happen when invoked from eeschema.
I have a (nonsensical) table in my homedir:
$ cat ~/prj-fp-lib-table
(fp_lib_table
(lib (name foo)(type KiCad)(uri bar)(options "")(descr ""))
)
and I get an error dialog for this only when opening a .net file.