On Fri, 04 Oct 2013 13:21:13 GMT, Sönke Ludwig wrote:

It's planned to build each package separately, but the schedule for that is not yet clear due to a lack of manpower. However, you can work around it with a little manual modification of GTkD's package.json. Conceptually it would look like this:

{
  "name": "gtkd",
  "importPaths": ["src"],
  "configurations": [
    {
      "name": "library",
      "targetType": "library",
      "sourcePaths": ["src"]
    },
    {
      "name": "prebuiltLibrary",
      "targetType": "sourceLibrary",
      "dflags-posix": ["-L$PACKAGE_DIR", "-lgtkd"],
      "sourceFiles-windows-x86": ["gtkd.lib"]
    }
  ]
}

Then run "dub build" once in the GtkD directory and use "subConfigurations": {"gtkd": "prebuiltLibrary"} in dependent projects.

Disclaimer: I haven't actually tested this. It should work in principle but there may be some wrong details in the draft.

This workaround operates well with projects without subpackages. I realized that subpackages are built into one huge lib file anyway (Is this expected behavior or temporally solution?).

It's planned to build each package separately, but the schedule for that is not yet clear due to a lack of manpower.

The most proper way i found is help you with that issue. Are there any pitfalls to know before forking and creating pull request?