2021. 07. 12. 18:01 keltezéssel, Khem Raj írta:
On 7/12/21 8:19 AM, Gregory Anders wrote:
Hello all,
I wrote and maintain a recipe to provide scipy in the OpenEmbedded build system [1]. I
would like to upstream this recipe into meta-python so that it is more broadly available
to those who need it as well as to reduce my own maintenance burden.
Before sending a patch, however, I'd like to solicit feedback from the meta-oe community
on how best to integrate this recipe into the meta-openembedded project. If you look at
the source for the recipe at [1] you will see that there are a few steps/hacks that need
to be done in order to get scipy to correctly cross-compile:
1. We have to add a CMake parameter to lapack ("-DCBLAS=ON"). This causes LAPACK to
build the C BLAS library instead of the Fortran BLAS library. This is necessary as scipy
tries to link against `cblas_*` functions.
FYI, there's another layer (https://github.com/tuxable-ltd/meta-scikit-learn
that
I had to fork and make hardknott-compatible) that uses python3-scipy as a build
and runtime dependency for python3-scikit-learn so import sklearn.linear_model"
is possible. That layer also extends python3-scipy with a native build variant
which doesn't exist in your layer AND patches lapack further to use openblas.
2. We have to patch numpy to force it not to include rpaths in the compiled shared
object file. Otherwise the bitbake QA fails as it detects rpaths from the build system.
3. Two variables must be set in either the local.conf or distro.conf file to enable
Fortran support. These can't be added in the scipy recipe directly (at least, last time
I tried it they couldn't be) so users have to manually add these themselves.
I am by no means an expert in bitbake or in the broader OE build environment. If you
know of a better solution to any of the problems outlined above, please share them. I am
also more than happy to provide more detail if anyone has any questions.
Ultimately, the ideal goal is to have a single 'python3_scipy.bb' recipe file that I can
send as a patch for inclusion in the meta-python layer rather than maintaining an
entirely separate meta-scipy layer.
I think meta-python is right layer for this.
Thanks!
Greg
[1]: https://github.com/gpanders/meta-scipy
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#92188):
https://lists.openembedded.org/g/openembedded-devel/message/92188
Mute This Topic: https://lists.openembedded.org/mt/84155703/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
