aBothe
Dub package configuration target problem.
Hi!
In my app solution I have a dependency on userman, a dub package that has two possible configurations: application and library. In MonoDevelop I keep changing the configuration of userman to library in the solution options menu, save the solution by clicking OK and every time I reopen my app solution, the configuration of userman is back to application. I have to say that before trying to edit this in MD I already hard coded the target as library in my app dub config file... but no luck.
When building with dub through the command line the target is respected.
my setup: MonoDevelop 5.7, D language binding 2.5.2, DUB 0.9.22, Debian 7.1 64 bit.
thx,
olivier
In the dub.json of your main project, where do you specify userman's used configuration? Despite that, what's the kind of misbehaviour you see? What's the actual bug?
... "dependencies": { "userman": "~>0.2.1", "vibe-d": "0.7.21-rc.2" }, "subConfigurations": { "userman": "library" }, ...
Oh, subconfigurations - I haven't touched this topic yet. Anyway, mono-d only invokes dub on the highest possible project in the dependency tree, so dub shall care about building dependencies rather than mono-d itself. So building everything shouldn't be a big problem then, right?
No building is good. I just thought it was a good idea to document encountered "glitches".
Thx for the quick answers.
Ah okay, so if there's such subconfiguration given, mono-d shall interpret it and pre-select e.g. the 'library' configuration. Okay then :)