meta-speech-framework: Update Alexa Auto SDK to v2.3 - meta-agl-devel - meta-agl-devel (Development and Community BSPs)

diff options

author	Scott Murray <scott.murray@konsulko.com>	2020-09-08 13:23:42 -0400
committer	Jan-Simon Moeller <jsmoeller@linuxfoundation.org>	2021-02-05 14:56:52 +0000
commit	8bf3c50ab7eb48f8db63ea41d6a12e32f3633dee (patch)
tree	acf5541f19ca2a40ef1361e0757485d91e0b05c6 /meta-egvirt/README.md
parent	d369fae7ef2e0bcbd934c838145b08a443b414ff (diff)

meta-speech-framework: Update Alexa Auto SDK to v2.3koi_11.0.1 koi_11.0.0 koi_10.93.1 koi/11.0.1 koi/11.0.0 koi/10.93.1 11.0.1 11.0.0 10.93.1

Changes: - Mask out the duplicate libopus recipe, the same version is available from a recipe in meta-oe. - Update BBFILES addition for the audio module in the feature template to work with yet another new audio output backend. - Update the AlexaAutoCoreEngineConfig.json.in template based on the new sample JSON in 2.3. - Update alexa-voiceagent-config recipe to add new configuration variables ALEXA_LOCALE, ALEXA_TIMEZONE, ALEXA_MFG_NAME, and ALEXA_DESCRIPTION to match requirements of the updated configuration JSON. - Remove local alexa-voiceagent-service patches merged by Amazon, and update 0001-remove-library-dependency-copying.patch for 2.3. - Update SDK module DEPENDS for alexa-voiceagent-service recipe to match what seems required now with 2.3. - Remove avs-device-sdk patch for building with g++ 9.x, as it is no longer required. - Add avs-device-sdk patch to workaround hang seen on first connection. - Add bbappends for aac-module-car-control and aac-module-messaging recipes to fix their nlohmann-json DEPENDS to work with the recipe that is available in meta-oe. - Rework aac-module-system-audio.bbappend to enable the PipeWire support that has been merged into the module. Bug-AGL: SPEC-3783 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: I18c910f9cbf874fef85d1d84508f6666d53629ed (cherry picked from commit e0d5ad833e89f47c88601e15158015319e568af8)

Diffstat (limited to 'meta-egvirt/README.md')

0 files changed, 0 insertions, 0 deletions

# XDS - X(cross) Development System Server XDS-server is a web server that allows user to remotely cross build applications. The first goal is to provide a multi-platform cross development tool with near-zero installation. The second goals is to keep application sources locally (on user's machine) to make it compatible with existing IT policies (e.g. corporate backup or SCM). This powerful webserver (written in [Go](https://golang.org)) exposes a REST interface over HTTP and also provides a Web dashboard to configure projects and execute only _(for now)_ basics commands. XDS-server also uses [Syncthing](https://syncthing.net/) tool to synchronize projects files from user machine to build server machine or container. > **NOTE**: For now, only Syncthing sharing method is supported to synchronize projects files. > **SEE ALSO**: [xds-make](https://github.com/iotbzh/xds-make), a wrapper on `make` command that allows you to build your application from command-line through xds-server. ## How to build ### Dependencies - Install and setup [Go](https://golang.org/doc/install) version 1.7 or higher to compile this tool. - Install [npm](https://www.npmjs.com/) : `sudo apt install npm` - Install [gulp](http://gulpjs.com/) : `sudo npm install -g gulp-cli` ### Building Clone this repo into your `$GOPATH/src/github.com/iotbzh` and use delivered Makefile: ```bash mkdir -p $GOPATH/src/github.com/iotbzh cd $GOPATH/src/github.com/iotbzh git clone https://github.com/iotbzh/xds-server.git cd xds-server make all ``` And to install xds-server in /usr/local/bin: ```bash make install ``` ## How to run ## Configuration xds-server configuration is driven by a JSON config file (`config.json`). Here is the logic to determine which `config.json` file will be used: 1. from command line option: `--config myConfig.json` 2. `$HOME/.xds/config.json` file 3. `<xds-server executable dir>/config.json` file Supported fields in configuration file are: ```json { "webAppDir": "location of client dashboard (default: webapp/dist)", "shareRootDir": "root directory where projects will be copied", "syncthing": { "home": "syncthing home directory (usually .../syncthing-config)", "gui-address": "syncthing gui url (default http://localhost:8384)" } } ``` >**NOTE:** environment variables are supported by using `${MY_VAR}` syntax. ## Start-up Use `xds-start-server.sh` script to start all requested tools ```bash /usr/local/bin/xds-start-server.sh ``` >**NOTE** you can define some environment variables to setup for example config file `XDS_CONFFILE` or change logs directory `LOGDIR`. See head section of `xds-start-server.sh` file to see all configurable variables. ## Debugging ### XDS server architecture The server part is written in *Go* and web app / dashboard (client part) in *Angular2*. ``` | +-- bin/ where xds-server binary file will be built | +-- config.json.in example of config.json file | +-- glide.yaml Go package dependency file | +-- lib/ sources of server part (Go) | +-- main.go main entry point of of Web server (Go) | +-- Makefile makefile including | +-- README.md this readme | +-- scripts/ hold various scripts used for installation or startup | +-- tools/ temporary directory to hold development tools (like glide) | +-- vendor/ temporary directory to hold Go dependencies packages | +-- webapp/ source client dashboard (Angular2 app) ``` Visual Studio Code launcher settings can be found into `.vscode/launch.json`. ## TODO: - replace makefile by build.go to make Windows build support easier - add more tests - add more documentation


context:
space:
mode: