Commit 79a0425b authored by Fernando Herrero's avatar Fernando Herrero
Browse files

Do not make firmware automatically. Add make firmware in CI yml. Add firmware dependency in README

parent ee1703f0
Pipeline #3906 failed with stages
in 46 seconds
......@@ -14,6 +14,7 @@
- cd build
- cmake -D CMAKE_BUILD_TYPE=RELEASE -DCPACK_PACKAGE_VERSION=$CI_COMMIT_TAG ..
- make package -j $(nproc)
- make firmware -j $(nproc)
artifacts:
paths:
- build/*.deb
......@@ -26,6 +27,6 @@
script:
- cd build
- "scp -i /root/.ssh/iriLabKeyNopwd -r *battery-monitor*.deb irilabo@147.83.76.226:packages/"
- "ssh irilabo@147.83.76.226 -i /root/.ssh/iriLabKeyNopwd -tt /home/irilabo/repo_scripts/update_repo.sh name-with-dashes"
- "ssh irilabo@147.83.76.226 -i /root/.ssh/iriLabKeyNopwd -tt /home/irilabo/repo_scripts/update_repo.sh battery-monitor"
only:
- tags
......@@ -63,6 +63,10 @@ This package also requires of the following IRI libraries:
* [iriutils](https://gitlab.iri.upc.edu/labrobotica/algorithms/iriutils "iriutils gitlab page"), a set of basic tools.
* [comm](https://gitlab.iri.upc.edu/labrobotica/drivers/comm "comm gitlab page"), a set of drivers for standard communication devices.
* [dynamixel](https://gitlab.iri.upc.edu/labrobotica/drivers/dynamixel "dynamixel gitlab page"), a driver for dynamixel communication protocol.
This package also contains the following packages as Git Submodules:
* [avr8_smbus_battery_monitor](https://gitlab.iri.upc.edu/labrobotica/firmware/avr8_smbus_battery_monitor), a firmware to read battery information through SMBUS
## Compilation and installation
......
......@@ -57,7 +57,7 @@ if(NOT EXISTS "${PROJECT_SOURCE_DIR}/${firmware_dir}/Makefile")
message(FATAL_ERROR "The submodules were not downloaded! GIT_SUBMODULE was turned off or failed. Please update submodules and try again.")
endif()
add_custom_target(firmware ALL COMMAND make
add_custom_target(firmware COMMAND make
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/../${firmware_dir}
)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment