Why can meson find hunt-net but not hunt-proton in dependency resolution?

Heromyth bitworld at qq.com
Wed Apr 1 01:56:26 UTC 2020

On Wednesday, 1 April 2020 at 01:21:22 UTC, YD wrote:
> On Tuesday, 31 March 2020 at 19:59:25 UTC, YD wrote:
>> [...]
> So I found that the issue is that dub.json file in hunt-proton 
> has an entry referring to the parent package with a relative 
> file path in it. When that relative file path is removed, Meson 
> can find hunt-proton.
> However, even after Meson found it, there are two bad behaviors:
> (1) Meson refused to automatically add the dependencies of 
> hunt-proton, and I had to manually add them to meson.build.
> (2) Meson did not automatically add the appropriate 
> d_module_versions setting that is required by hunt (the 
> HAVE_EPOLL/HAVE_IOCP/... setting), and I had to manually add 
> that too.
> Anyway, after manually tweaking the meson.build file like 
> above, I got it to work (except that compiling/linking seems 
> quite slow).

Sorry for the inconveniences. We are still testing Hunt-AMQP. The 
problems about dub.json will be fixed soon.

More information about the Digitalmars-d-learn mailing list