Michel Hidalgo

@dirk-thomas if you happen to have a bit of free time (if that even exists :sweat_smile:), would you take a look and share your thoughts? I'd very much appreciate it.

> The rational is that `node-gyp` for example contains many platform specific and other conditional configurations Would you mind sharing an example? I'd like to understand where the difficulties show...

> I think the design doc could really use a diagram of how all the data flows. @sloretz Agreed. > It seems like the .cps generation is separated from the...

> I did some research on the build systems for some language bindings. @koonpeng Thank you ! > 1. nodejs: uses node-gyp, lots of conditionals https://github.com/nodejs/node-gyp/blob/master/addon.gypi. It has several conditionals,...

> What if I run `ament_meta_build with --build-system node-gyp`? It must know all the conditionals and implicit flags added by `distutils` to generate the `.gypi` file, we probably also need...

> I thought it was to support generating build system files for any language with CBS, but is it correct that the goal is actually just to support many code...

> An example of the problem I faced is that node-gyp knows how to build a node module, but doesn't know the link libraries. cmake knows the link libraries but...

@peterpolidoro Interesting, I didn't know about Guix. I would have to look into it in more depth. I will say that revamping ROS 2's package management system is ~way~ massively...

I've address some comments and questions by clarifying the proposal. It's still lacking a nice diagram and examples. I'll add those next.

> how about providing the plugins a function to resolve a message/package's required build flags? @koonpeng at the package-level, that information can be propagated by the build system. I understand...