Merge branch 'splitio_base' of https://github.com/rerdavies/pipedal into dev_splitio_merge
This commit is contained in:
@@ -21,6 +21,7 @@ Run the following commands to install dependent libraries required by the PiPeda
|
||||
|
||||
sudo apt update
|
||||
sudo apt upgrade
|
||||
|
||||
sudo apt install -y liblilv-dev libboost-dev \
|
||||
libsystemd-dev catch libasound2-dev uuid-dev \
|
||||
authbind libavahi-client-dev libnm-dev libicu-dev \
|
||||
|
||||
@@ -13,15 +13,16 @@ available through the Code plugins store) has configured itself, build commands
|
||||
If you are not using Visual Studio Code, you can configure, build and install PiPedal using CMake build tools. For your convenience,
|
||||
the following shell scripts have been provided in the root of the project.
|
||||
|
||||
./init.sh # Configure the CMake build for the first time, or if you
|
||||
./init.sh # Configure the CMake build for the first time, or if you
|
||||
# have changed one of the CMakeList.txt files. (release build)
|
||||
|
||||
./mk.sh # Build all targets (release build)
|
||||
|
||||
sudo ./install.sh # Deploy all targets
|
||||
sudo ./install.sh # Deploy all targets
|
||||
|
||||
sudo ./makePackage.sh # Build a .deb file for distribution.
|
||||
|
||||
|
||||
If you are using a development environment other than Visual Studio Code, it should be fairly straightforward to figure out how
|
||||
to incorporate the PiPedal build procedure into your IDE workflow by using the contents of the build shell scripts as a model.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user