Nicolás Ojeda Bär

Thanks for the explanations @dra27!

Sorry for the naïve question, but as the issue description above mentions native code, what "debug symbols" are we talking about? The location information for each instruction?

What do people think about this request? The current implementation of `Filename` already defines the modules for each system, it would be just a matter of exposing them in the...

(my own personal opinion is that indeed there are some cases where having these modules available would be useful, but it is not something that comes up very often).

I haven't looked carefully at all the attemps, but the first attempt should work if you add `(extra_deps ../lib-foo/foo.h)` to the `(foreign_stubs ...)` field: ``` ; prog/dune (executable (name prog)...

> I thought that this was precisely the job (one of the jobs) of the `foreign_archives` stanza? Maybe there is room for improvement here, but the `foreign_archives` stanza just means...

> My understanding was that `include_dirs` and `extra_deps` are used to track dependencies on files that (morally) are part of the (foreign stubs of the) _current_ library/executable object. As far...

I believe the simplest is attempt 1 + `(extra_deps ../lib-foo/foo.h)` to specify the dependency of `prog_stubs.c` on `foo.h`. Anyway cc-ing @snowleopard who implemented foreign library/stubs support (see #2650 for some...

> `target[s]` is optional, thanks! > > > (note: I wish stanzas were listed in alphabetic order in the stanza reference, they are hard to find in the list) >...

@bbatsov I think a PR would be the fastest way to make progress on this :) Personally it seems a good idea (especially as it is opt-in: it can be...