| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
| |
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
| |
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
|
|
|
|
| |
Place all of the host software python requirements into a config file.
This makes it easier to update the python requirements without having
to update several installation scripts.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
| |
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
| |
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
| |
|
|
|
|
|
| |
The gcc arm download sometimes fails - try to cache it within the
travis-ci system to prevent that.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
|
Move the travis installation steps from the travis-build.sh script to
a new script (scripts/travis-install.sh). Move the travis-build.sh
script to the scripts/ directory as well.
The data dictionaries built in the compile tests are useful during
host software testing, so run all the compile tests sequentially in a
single VM and save the data dictionaries after each build. Also,
build all the config files found in the test/configs/ directory.
Create the python virtualenv environment during the install phase and
invoke the klippy.py host software in the build phase to perform a
basic host software sanity check.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
