Inline files

Although the three sections in the buildfile above seem to be distinct, in reality all three are similar in that they're lists of files.

Notice also how the buildfile itself is structured:

optional_attributes filename optional_contents

For example, the line:

[virtual=armle-v7,srec] .bootstrap = {

has an attribute of [virtual=armle-v7,srec] and a filename of .bootstrap. The optional_contents part of the line is what we call an inline file; instead of getting the contents of this file from the host machine, mkifs gets them from the buildfile itself, enclosed by braces. The contents of the inline file can't be on the same line as the opening or closing brace.

Let's examine these elements in some detail.