Dylan Baker
> I notice in the meson-log.txt file that the archiver is used instead of the linker when detecting linker : > ```Detecting linker via: `d:/Bitbucket/Tools_Inv_HMC_IDM\Compiler\ctc\bin\artc.exe --version` -> 0 stderr: TASKING...
Other than the loop thing, this looks super reasonable to me.
Rather than a module, a custom dependency would be the most correct thing. You might be able to use a `cmake` dependency (`dependency('DiaSDK', method='cmake')`), though no guarantees that would work....
I'd put it in dev.py, yeah. If you run into any issues feel free to ping this or ping me on IRC/Matrix. I wrote that giant blob of text, so...
Right now our C# support is super bare bones, so unless you want to spend a lot of time working on Meson + C# stuff, I wouldn't worry about that...
I just checked what happens with `custom_target`s, and they have the same behavior, so I think this might be "working as expected"?
Yeah, I think that's perfectly reasonable.
There's actually a fixme about doing this in the ninja backend.
I think dumpbin /symbols might work
meson has a `vs_module_def` keyword argument for the `executable()` or `shared_library()` in question. Generally you would either check the .def file in and pass it as a string `executable(..., vs_module_def...