On 1/17/26 6:34 PM, James Le Cuirot wrote:
> Sometimes it is necessary to give Meson configuration beyond what the
> eclass currently writes to the .ini files. Multiple native and cross
> files can be specified, and Meson will use them all. The only rule is
> that you cannot repeat a section within the same file.
> 
> The given argument is used to form the filename for the .ini file. It is
> important for the filename to be unique because timestamp changes will
> trigger a reconfigure.
> 
> meson_append_file uses either --native-file or --cross-file depending on
> whether we're cross-compiling (including multilib) or not.


- "append" gives entirely the wrong messaging; reading this I assumed it
  would concat new text to the original "internal eclass" one

- "meson_append_file" -- meson.eclass function which "appends" a "file"?
  Call it meson_add_machine_file. (and meson_add_native_file)



-- 
Eli Schwartz

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to