Unnamed repository; edit this file 'description' to name the repository. http://git.gnuabordo.com.br/meson.git/atom?h=master 2024-07-31T14:31:26+00:00 2024-07-31T14:31:26+00:00 Nirbheek Chauhan nirbheek@centricular.com 2024-07-29T03:33:01+00:00 urn:sha1:bdc2f2774c35ad2c81e3fea8621fdff6905c021b 2024-07-30T21:40:41+00:00 Dylan Baker dylan@pnwbakers.com 2024-07-30T20:30:16+00:00 urn:sha1:a51be6b1c77cba06bec3f27cdb846e825e958c55 Instead of storing the generated header cache in the Target, store it in the NinjaBackend, as it really is just data for the NinjaBackend to use. 2024-07-30T19:28:43+00:00 Eli Schwartz eschwartz93@gmail.com 2024-07-30T01:22:37+00:00 urn:sha1:03a8f35031c9ae0ded162f8b228c5b3f04643632 By default, we build with debug info which can be useful for investigating why a test segfaults instead of either passing or failing. The nasm language hooks this up, but using nasm as a generator program does not. Bug: https://bugs.gentoo.org/936911 2024-07-30T19:28:43+00:00 Eli Schwartz eschwartz93@gmail.com 2024-07-29T15:00:54+00:00 urn:sha1:a05b790d6600586449471d3fe957442896dec2a7 The command we use to heuristically parse whether it is dirty by interpreting prose descriptions of the repository state, is vulnerable to changes in locale resulting in failing to match the English word that means it is clean. Unfortunately, I am no mercurial expert so I am unaware if mercurial supports scripting, like git does. Perhaps the technology simply does not exist. A quick attempt at searching for the answer turned nothing up. It appears that #4278 had good cause indeed for using this prose parsing command. So, we simply sanitize the environment due to lack of any better idea. Bug: https://bugs.gentoo.org/936670 2024-07-30T18:13:12+00:00 Eli Schwartz eschwartz93@gmail.com 2024-07-28T17:37:35+00:00 urn:sha1:077d540c10a103fd5a41d0747b8140fef87b02ef 2024-07-30T18:13:12+00:00 Eli Schwartz eschwartz93@gmail.com 2024-02-12T01:19:27+00:00 urn:sha1:28ab1ce39a7889c681cf6874f9062baa97b1f5f7 In particular, it is only ever constructed once, and all but two of its arguments are always passed. So there's no reason or valid justification to initialize them as None or pretend that you have to check them for None values. Nor in fact does the command list need to be a default_factory. There are also two instance attributes which it is never instantiated with, but which are tracked after the fact. Don't add this to the signature for `__init__` as that is misleading. 2024-07-30T18:13:12+00:00 Eli Schwartz eschwartz93@gmail.com 2024-02-12T00:50:26+00:00 urn:sha1:a59231ff4a30f686306662e1298c69fd2459dec8 None sentinel is replaced by field(), so we don't need to declare it Optional anymore. 2024-07-30T18:13:11+00:00 Eli Schwartz eschwartz93@gmail.com 2024-06-05T02:05:57+00:00 urn:sha1:4a352dd8bdb083b2d75994fe1b0ba27242a7ce61 2024-07-30T18:13:11+00:00 Eli Schwartz eschwartz93@gmail.com 2024-07-30T04:20:07+00:00 urn:sha1:574fbe7d95cc8f82492ff60fe34868def749c4f1 create_target_linker_introspection is only ever called from one place, which passes in CompilerArgs. This was implemented in commit 5eb55075baa2883170a3d0cf3c0621aae56a1632 which performed this conversion as a preventative measure, since its type was not obvious (and thereby modified the *type* of the variable in place). 2024-07-30T18:13:11+00:00 Eli Schwartz eschwartz93@gmail.com 2024-07-30T03:17:22+00:00 urn:sha1:823779a9b1b39afb061d9ecf597aa96ab2ceb07b If it exists, we want to know it has the right type when we use it in ninjabackend.py.