RejectedSoftware Forums

On 2016-02-18 14:18, Alex Simonov wrote:

How to properly use options "subConfigurations" with subpackage "vibe-d:core"?

When I write in dub.json "subConfigurations": {"vibe-d": "win32"} and run dub build I receive messages

<...>
vibe-d:data 0.7.27: target for configuration "library" is up to date.
vibe-d:core 0.7.27: target for configuration "libevent" is up to date.
<...>
vibe-d 0.7.27: building configuration "win32"...

and I get dependency on libevent.

I tried to change "subConfigurations": {"vibe-d:core": "win32"}, {"vibe-d": "win32", "vibe-d:core": "win32"}, etc. But I still get dependency on libevent.

How to build "win32" configuration?

I think it's a bug [1]. As a workaround you can remove the cached
packages. That is ~/.dub/packages on Posix, not sure where it's stored
on Windows.

[1] https://github.com/rejectedsoftware/vibe.d/issues/1418

/Jacob Carlborg

On Fri, 19 Feb 2016 10:06:40 GMT, Sönke Ludwig wrote:

On Thu, 18 Feb 2016 21:25:55 +0100, Jacob Carlborg wrote:

On 2016-02-18 14:18, Alex Simonov wrote:

How to properly use options "subConfigurations" with subpackage "vibe-d:core"?

When I write in dub.json "subConfigurations": {"vibe-d": "win32"} and run dub build I receive messages

<...>
vibe-d:data 0.7.27: target for configuration "library" is up to date.
vibe-d:core 0.7.27: target for configuration "libevent" is up to date.
<...>
vibe-d 0.7.27: building configuration "win32"...

and I get dependency on libevent.

I tried to change "subConfigurations": {"vibe-d:core": "win32"}, {"vibe-d": "win32", "vibe-d:core": "win32"}, etc. But I still get dependency on libevent.

How to build "win32" configuration?

I think it's a bug [1]. As a workaround you can remove the cached
packages. That is ~/.dub/packages on Posix, not sure where it's stored
on Windows.

[1] https://github.com/rejectedsoftware/vibe.d/issues/1418

I'll look into that next. Using "subConfigurations": {"vibe-d:core": "win32"} is also a possible workaround (didn't test), but it requires adding an explicit dependency to "vibe-d:core", or it will be ignored (diagnostics really need to be improved there).

It's properly build with "dependencies": {"vibe-d:core": "0.7.27"}, "subConfigurations": {"vibe-d:core": "win32"}.

I think depending on sub packages is the result of a full separation of the individual library components.