Hello!

I've made a modification in poky/meta/classes/libc-package.bbclass (
shown below)

However I don't want this change to be stored here long term and
instead feel that it should live in my project specific layer,
meta-hon-grip.

After checking with bitbake-layers, I saw that my layer has a higher
priority than the poky layer so my layer should be checked first ( or
so I thought)

I copied the modified version of libc-packages.bbclass into
meta-hon-grip/classes and I restored the version in the poky layer to
its original state.

After making this change, I found that the modified version in my
layer is not being used and instead the version in the poky layer is
the one in play.

I'm trying to figure out what else to try.

Any suggestions would be greatly appreciated!

Thank you,

Davis

diff --git a/meta/classes/libc-package.bbclass
b/meta/classes/libc-package.bbclass
index 467d567..72d447a 100644
--- a/meta/classes/libc-package.bbclass
+++ b/meta/classes/libc-package.bbclass
@@ -287,7 +287,7 @@ python package_do_split_gconvs () {
                 bb.error("locale_arch_options not found for
target_arch=" + target_arch)
                 raise bb.build.FuncFailed("unknown arch:" +
target_arch + " for locale_arch_options")

-            localedef_opts += " --force --old-style --no-archive --prefix=%s \
+            localedef_opts += " --force --no-archive --prefix=%s \
                 --inputfile=%s/%s/i18n/locales/%s --charmap=%s %s/%s" \
                 % (treedir, treedir, datadir, locale, encoding,
outputpath, name)

@@ -295,7 +295,7 @@ python package_do_split_gconvs () {
                 (path, i18npath, gconvpath, localedef_opts)
         else: # earlier slower qemu way
             qemu = qemu_target_binary(d)
-            localedef_opts = "--force --old-style --no-archive --prefix=%s \
+            localedef_opts = "--force --no-archive --prefix=%s \
                 --inputfile=%s/i18n/locales/%s --charmap=%s %s" \
                 % (treedir, datadir, locale, encoding, name)
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to