Directory structure, hierarchy of files, and executables

I’m wondering why the file structure from the apt repository is different from my installation (built from source). I’m not talking about the /usr/local prefix.
For Debian 11 bullseye-backports.

  1. For example, in the apt deb package, the files that start with the underscore (_gerbview.kiface, _pcbnew.kiface, etc) in $PREFIX/bin are symlinked to the same name parent file, which is located in $PREFIX/lib/kicad.

With my build, the .kiface files are just in $PREFIX/bin, not symlinked. $PREFIX/lib Only has kicad/plugins/3d/libs3d_ (idf.so, oce.so and vrml.so)

$PREFIX/lib also has libkicad_3dgs.so symlinked to libkicad_3dgs.so.2.0.0. This is the same as the apt package, except with my build, it’s in the aarch64-linux-gnu folder. I don’t think this matters.

  1. Another example, for the apt package, pcbnew.py is in $PREFIX/lib/python3/dist-packages. Another file there is _pcbnew.cython-39-aarch64-linux-gnu.so. Non executables.

For my build, $PREFIX/lib/python3.9/site-packages has pcbnew.py, but another file _pcbnew.so is a symlink to $PREFIX/bin/_pcbnew.kiface.

I think I understand why site-package/dist-package directory is different (Debian python file structure). But I don’t get the files.

  1. in $PREFIX/share for the apt package, I see many things but most important : python3/runtime.d/kicad.rtupdate.
    I don’t have this.

$PREFIX/share Also has kicad/scripting/plugins/ files are not executable for the apt package, but I have them as executable.

Is this a problem for me? Please help me understand these things.

Thanks in advance.

Rpi 4b 8GB 64-bit aarch64 build
Built with OCC 7.6, wxpython 4.2.0, wxwidgets 3.2.1, EGL backend, bundled GLEW, and on master branch 6.99.
Used cmake 3.24 and ninja 1.11.
Gcc 12.2.0 g++12.2.0 cpp 12.2.0

Edit:
I have cython installed from pip (0.29.32)
The apt repo cython3 for stable has 0.29.21, so I didn’t get it.
I’m now seeing that cython3 from apt repo for unstable (0.29.32-1) requires python 3.10….I wonder if this has to do with the wxpython version circular import error regarding the pcbnew scripting console. I have another post about it.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.