gdbus-codegen-glibmm: Fix build issue for hard-coded version

Pelagicore / meta-bistro

Yocto layer providing In-Vehicle Infotainment related functionality and adaptations

MIT License

14 stars 21 forks source link

gdbus-codegen-glibmm: Fix build issue for hard-coded version #231

Closed thenor closed 5 years ago

thenor commented 5 years ago

The sed script in the inc file had a hard-coded version number, but if we would like this recipe to be more future proof and be able to handle more than one version of the tool, then we need to fetch the version nr from somewhere.

The solution is to name the bb file after the major version of the tool and fetch the number in the inc file.

Signed-off-by: Therese Nordqvist therese.nordqvist@pelagicore.com

sashko commented 5 years ago

Why mainstream not using python3?

martin-ejdestig commented 5 years ago

Why mainstream not using python3?

It is using python3. The 2/3 suffix is for the tool itself.

martin-ejdestig commented 5 years ago

But suffix is there for a similar reason as it is in python2/3. API stability is guaranteed on X. X+1 indicates API breakage.