e3053f2176
Due to the CONF_ENV options set in the gst1-python.mk file, libpython-dir must be set manually or else the error: "Python dynamic library path could not be determined" occurs. Previously the libpython-dir option was set to $(HOST_DIR)/lib/python$(PYTHON3_VERSION_MAJOR), however, this breaks the resulting .so because the above full path is baked into the resulting .so. which results in the error: Couldn't g_module_open libpython. Reason: /full/path/to/host/lib/python3.8/libpython3.8.so: cannot open shared object file: No such file or directory To fix this error, set the libpython-dir to /usr/lib. Because we provide PYTHONPATH=$(PYTHON3_PATH) in the GST1_PYTHON_CONF_ENV, the logic in the meson file uses the above python3 provided by the PYTHONPATH variable to determine /usr/lib/ has the proper python$(PYTHON3_VERSION_MAJOR).so file. Because Buildroot provides the appropriate paths, the meson file finds the correct .so file and the resulting compiled library has the appropriate path of /usr/lib/python3.$(PYTHON3_VERSION_MAJOR).so This change has been tested on the following distributions: - Debian 9 and 10 - Debian 9 without python3 installed on the host. - Centos7 - Fedora 31 Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitlab-ci.yml.in | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches