>>>>> "MC" == Michael Cronenworth <mike@xxxxxxxxxx> writes: MC> Any long term plans to support C/C++ apps? Depends on what you mean by "support", really. Really there's just a new spec section that gets run and it just needs to echo a list of build dependencies. That's really all this does; the existing Rust support just hides the script within %cargo_generate_buildrequires. (Honestly I'm disappointed that the macro doesn't emit the %generate_buildrequires line as well; the pattern used by Rust currently builds in the assumption that the generator will be a shell script.) If there are more general methods for extracting build dependencies from various build systems which can be stuffed into macros, then by all means we should be adding them. MC> I know those are all over the map with regards to build tools, but MC> maybe cmake/meson could be supported? Well, how do those list build dependencies? How would you extract them and convert them to package names (or something else which is provided by the target packages)? - J< _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
