From f7307e90633a776112ec4f0d57fa189b1e6ede9f Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Fri, 30 Nov 2018 16:13:11 +0000 Subject: Revert "doc: Improve formatting" This reverts commit 60b0f4556fb94cbd6d9bac083f561067a437d98e. Change-Id: Id73104aa7466e6a16ec6a93842718017a2084584 Signed-off-by: Romain Forlot --- docs/dev_guide/5_autobuild.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) (limited to 'docs/dev_guide') diff --git a/docs/dev_guide/5_autobuild.md b/docs/dev_guide/5_autobuild.md index 6ff93df..6977e09 100644 --- a/docs/dev_guide/5_autobuild.md +++ b/docs/dev_guide/5_autobuild.md @@ -19,18 +19,14 @@ 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 +* '#!/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