kernel version selection uses build machine rather than target #256
Assignees
Labels
Comments
|
@RobertCNelson any suggestions on how this could be handled? thanks! |
|
@pdp7 sorry, i hack around that too.. one of my fast arm builders used a v3.14.x based kernel.. Yes, it should be an export option.. (defaults to 4.1.x+ ;) ) Regards, |
eigendude
added a commit
to eigendude/adafruit-beaglebone-io-python
that referenced
this issue
Apr 17, 2019
This fix uses the 'setup.cfg' file used by setuptools. It reads an Adafruit-specific section that is ignored by setuptools. The reason for using the config file is that command-line parameters can't be passed to setup.py, as the command-line is ideally opaque to the installer. 'setup.cfg' was added to setuptools as a useful middle-ground between modifying 'setup.py' and the command-line. Now, library build systems can modify a config file instead of the source directly. Fixes adafruit#256
eigendude
added a commit
to eigendude/adafruit-beaglebone-io-python
that referenced
this issue
Apr 17, 2019
This fix uses the 'setup.cfg' file used by setuptools. It reads an Adafruit-specific section that is ignored by setuptools. The reason for using the config file is that command-line parameters can't be passed to setup.py, as the command-line is ideally opaque to the installer. 'setup.cfg' was added to setuptools as a useful middle-ground between modifying 'setup.py' and the command-line. Now, library build systems can modify a config file instead of the source directly. Fixes adafruit#256
eigendude
added a commit
to eigendude/adafruit-beaglebone-io-python
that referenced
this issue
Apr 17, 2019
This fix uses the 'setup.cfg' file used by setuptools. It reads an Adafruit-specific section that is ignored by setuptools. The reason for using the config file is that command-line parameters can't be passed to setup.py, as the command-line is ideally opaque to the installer. 'setup.cfg' was added to setuptools as a useful middle-ground between modifying 'setup.py' and the command-line. Now, library build systems can modify a config file instead of the source directly. Fixes adafruit#256
eigendude
added a commit
to eigendude/adafruit-beaglebone-io-python
that referenced
this issue
Apr 17, 2019
This fix uses the 'setup.cfg' file used by setuptools. It reads an Adafruit-specific section that is ignored by setuptools. The reason for using the config file is that command-line parameters can't be passed to setup.py, as the command-line is ideally opaque to the installer. 'setup.cfg' was added to setuptools as a useful middle-ground between modifying 'setup.py' and the command-line. Now, library build systems can modify a config file instead of the source directly. Fixes adafruit#256
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
library version: master:
commit 49b2be3 (HEAD -> master, origin/master, origin/HEAD)
Merge: 6f3589a e9c70f7
Author: Drew Fustini drew@pdp7.com
Date: Sun Feb 18 02:04:43 2018 -0600
The library supports two kernel interfaces, and the detection of this is in setup.py:
kernel = platform.release()
if kernel >= '4.1.0':
kernel41 = [('BBBVERSION41', None)]
else:
kernel41 = None
I am cross-compiling. So the kernel version detected is from my build machine. This means I have to use a pre-4.1.0 kernel to build for a pre-4.1.0 target and a 4.1.0+ build kernel to build for a 4.1.0+ target.
The build should provide an option to specify a kernel build directory where 'make prepare' has been run, so that the kernel version the library supports is based on the target kernel version.
The text was updated successfully, but these errors were encountered: