From 60b0f4556fb94cbd6d9bac083f561067a437d98e Mon Sep 17 00:00:00 2001 From: José Bollo Date: Thu, 29 Nov 2018 16:09:15 +0100 Subject: doc: Improve formatting MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Id252624a59fffe789b93e978ef60eec2fc659055 Signed-off-by: José Bollo --- docs/dev_guide/5_autobuild.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/dev_guide/5_autobuild.md b/docs/dev_guide/5_autobuild.md index f6788fc..6ff93df 100644 --- a/docs/dev_guide/5_autobuild.md +++ b/docs/dev_guide/5_autobuild.md @@ -19,14 +19,18 @@ This script could be written in one of the following languages: * Bash * Python -The script will be executed directly after a chmod() on it (this implies that the caller should make the script executable before calling it: caller could be aglwgt.bbclass, a jenkins job, a 'real' developer ...) +The script will be executed directly after a chmod() on it (this implies that the +caller should make the script executable before calling it: caller could be +aglwgt.bbclass, a jenkins job, a 'real' developer ...) An appropriate shebang is required to make the script callable directly: * '#!/usr/bin/make -f' for Makefile format, * '#/usr/bin/bash' for Bash * etc. -The calling convention is close to the one from make, in particular to pass arguments through env variables. This is also easy for bash, as a simple eval on arguments will set environment variables correctly. +The calling convention is close to the one from make, in particular to pass +arguments through env variables. This is also easy for bash, as a simple eval +on arguments will set environment variables correctly. The generic call has the following format: ```bash -- cgit 1.2.3-korg