Is there such a thing as zero padding a number in a recipe (or vice versa?
I'd be just as happy starting with a zero-padded number, and converting it
to non-zero-padded.
The crux of the dilemma is that I must have zero-padding for file-naming,
but I CAN'T have zero padding in these numbers when I p
I'd like to be able to create a file using the cat command in a recipe.
The sub-goal is to have the file created somewhere I can actually find it:
do_create_tebf0808() {
cat > tebf0808.bif <--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.
That seems to work. Thanks!
On Fri, Jun 28, 2019 at 3:53 PM Burton, Ross wrote:
> The bash parser does have some bugs, and I think you just found one.
> Probably easier to have a template on disk in SRC_URI, and sed in the
> value you want.
>
> Ross
>
> On Fri, 28 Jun
[Sending again because I initially replied to Claudius only, and not
mailing list]
I found using back-ticks with printf also works in a recipe:
NUMBER = "1"
NUMBER_PADDED="FOO_`printf "02d" ${NUMBER}`_MOARFOO"
On Fri, Jun 28, 2019 at 4:48 PM Claudius Heine w
In short, I'd like to have my recipe know the name of a file that is a
symbolic link, as in "readlink" and the linux prompt.- preferably before
populating SRC_URI, but this is not working (so I guess random shell
scripts are not doable in recipes):
LINK_TARGET=`readlink -f ${LATEST_VER}`
SRC_URI =