'How do I escape a "$" in bitbake/yocto?

One of my recipes in Yocto need to create a file containing a very specific line, something like:

${libdir}/something

To do this, I have the recipe task:

do_install() {
    echo '${libdir}/something' >/path/to/my/file
}

Keeping in mind that I want that string exactly as shown, I can't figure out how to escape it to prevent bitbake from substituting in its own value of libdir.

I originally thought the echo command with single quotes would do the trick (as it does in the bash shell) but bitbake must be interpreting the line before passing it to the shell. I've also tried escaping it both with $$ and \$ to no avail.

I can find nothing in the bitbake doco about preventing variable expansion, just stuff to do with immediate, deferred and Python expansions.

What do I need to do to get that string into the file as is?

Solution 1:^[1]

By default this task will be executed as shell function via /bin/sh, but it depends on your system what it will be as you can have a symlink named /bin/sh pointing to bash. The BitBake's manual prevents from using bashism syntax though.

You can consider just adding this task in your recipe as python function:

python do_install () {
    with open('/path/to/your/file', 'a') as file:
        file.write('${libdir}/something')
}

'a' stands for append.

This should eliminate the problem with variable expansion.

Solution 2:^[2]

There is no standard way to escape these sorts of expressions that I am aware of, other than to try to break up the expression - accordingly this should work:

do_install() {
    echo '$''{libdir}/something' >/path/to/my/file
}

Solution 3:^[3]

The best solution is simply this:

bitbake_function() {
    command $libdir/whatever
}

Bitbake will only expand ${libdir}; $libdir is passed through verbatim.

We don't have to worry about dollar signs that are not followed by {, and in this case, there is no need for libdir to be wrapped in braces.

The only time we run into a problem with just $foo is if we have something like ${foo}bar where the braces are required as delimiters so that bar isn't included into the variable name. In that situation, there are other solutions, such as for instance generating the shell syntax "$foo"bar. This is less cryptic than resorting to \x24.

Solution 4:^[4]

If you need to use $ in variable assignment, remember that bitbake won't evaluate $whatever so you have to escape it for the underlying shell.

For instance I set gcc/ld Rpath option to use $ORIGIN keyword this way:

TARGET_LDFLAGS_append = " -Wl,-rpath-link=\\$$ORIGIN"

https://lists.yoctoproject.org/pipermail/yocto/2017-September/037820.html

Solution 5:^[5]

You can define a variable to be a literal dollar sign.

DOLLAR = "$"

do_install() {
    echo '${DOLLAR}{libdir}/something' >/path/to/my/file
}

no extra quoting required.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1
Solution 2	bluelightning
Solution 3
Solution 4	RzR
Solution 5	whence_heat

'How do I escape a "$" in bitbake/yocto?

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]