On 9/1/25 12:09, Alexander Kanavin wrote: > On Sat, 30 Aug 2025 at 22:58, Gyorgy Sarvari via > lists.openembedded.org <[email protected]> > wrote: >> In principle I think that it's about as I can make it on my own (sans AB >> failures[1]), but there would be a few question marks on my end: >> >> 1. If you have a better idea for relevant Makefile.in.in heurestics in >> autotools.bbclass, I'm listening >> 2. I *think* that the Makevars concatenation makes actual sense, and the >> build success is not only an accident - but I'm not 100% sure if that's >> the best way to handle this. If you know gettext, I'd like to hear your >> opinion. (This was inspired by gettextize's behavior. Upon running it, >> it copies the Makevars.template with default values in the po folder, >> and asks you to set up all the variables from it in your Makevars file) > First, thanks for working on this. Gettext recipe easily wins the > 'least sexy' award in oe-core. > > Second, the same discussion has stalled in previous update proposal > (to 0.24), after Ross suggested we should just try to use gettextize. > Ross, can you please comment? We do need to get this update in, and > maybe attempts to 'do things right' would be too counter productive.
Yes, briefly I was also looking also into gettextize, and I got to the same conclusion as Robert, it doesn't look that it would have more benefits than drawbacks. The current update logic in autotools.bbclass would be reduced by a line or two, but gettext-minimal-native recipe would be unusable, and all gettext using recipes would have a dependency on the full gettext package. Nevertheless, if there is interest, I could try to prepare a proposal using gettextize once the current of the patch gets in a state that doesn't blow up on AB.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#222853): https://lists.openembedded.org/g/openembedded-core/message/222853 Mute This Topic: https://lists.openembedded.org/mt/114982746/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
