It'd be better if the flatpak package didn't have to build python since python 3.10 is provided as part of the runtime/SDK (22.08)
python3 is included in the runtime, the command should be only be python3, not /app/bin/python3
pythonlibpath should take into account that some libraries are distributed in two places - /app/lib (modules included as part of the app) and in the runtime (/usr/lib). For example numpy isn't available in the runtime, so it is included with the app and goes to /app/lib
pythonincpath again similar to above. It should be /app/include and /usr/include
I've tried adding those as ['A', 'B'], but it didn't work.
https://github.com/esys-escript/esys-escript.github.io/blob/d036cf126c65d9ee799b54e476296ed7b06bf953/scons/flatpak_options.py#L35-L37
It'd be better if the flatpak package didn't have to build python since python 3.10 is provided as part of the runtime/SDK (22.08)
python3 is included in the runtime, the command should be only be
python3
, not/app/bin/python3
pythonlibpath
should take into account that some libraries are distributed in two places -/app/lib
(modules included as part of the app) and in the runtime (/usr/lib
). For example numpy isn't available in the runtime, so it is included with the app and goes to/app/lib
pythonincpath
again similar to above. It should be/app/include
and/usr/include
I've tried adding those as
['A', 'B']
, but it didn't work.pythonlibname='python3.10'
should be added. Otherwise it can't find python headers, see https://github.com/esys-escript/esys-escript.github.io/issues/96#issuecomment-1643071814