> Well, as I stated previously, flashrom built with meson results in the > `-o` option not working at all. When helping others via IRC, we > recommend fetching flashrom logs using that option so that no messages > get lost, so not being able to rely on it is rather inconvenient.
Ouch... Yeah, that shouldn't happen. > I can see [1] that you have two changes on gerrit, one of which is > currently not submittable due to merge conflicts and has not been > touched in two months. To be fair, that's not a lot of time when we're talking about flashrom... > Are there any > future plans for meson, such as making Jenkins build-test it? Edward > O'Callaghan is working on unit testing [2], and it would be great if > Jenkins could actually run these tests alongside the usual build > tests. There isn't a thing such as too much coverage, or is there? :-P Patrick already chimed in, w.r.t. Jenkins. Automating some QA has been on my todo list for a while, and I'm in between jobs at the moment so I'll finally have a bit of time to work on it :-) Overall I'd like to keep meson support working for fwupd. Like ChromeOS it's a valuable user that provides development, hardware support, and testing on realworld hardware at the cost of a few relatively minor bumps. It's better to work with those communities rather than them forking or reinventing flashrom. _______________________________________________ flashrom mailing list -- [email protected] To unsubscribe send an email to [email protected]
