December 24, 2019 Static linking, specifying binary and test-library folder | ||||
---|---|---|---|---|
| ||||
Hello, how does one: 1. Force static linking (build with `-defaultlib` flag) 2. Specify binary file generated by the `dub buid` command 3. Specify binary file generated by the `dub test` command in the `dub.json` file? |
December 24, 2019 Re: Static linking, specifying binary and test-library folder | ||||
---|---|---|---|---|
| ||||
Posted in reply to Adnan | On Tuesday, 24 December 2019 at 05:51:37 UTC, Adnan wrote: > Hello, how does one: > > 1. Force static linking (build with `-defaultlib` flag) Generally, when you don't see a buildOption in the docs for the compiler flag you want, use dflags. https://dub.pm/package-format-json.html > > 2. Specify binary file generated by the `dub buid` command targetPath, described under Build Settings in the docs. > > 3. Specify binary file generated by the `dub test` command You can override some of the settings for the build types (like the unittest build type), but targetPath is not one of them. https://dub.pm/package-format-json.html#build-types I would try to do it using a configuration. Name it whatever you want (perhaps "testing"). Set the targetPath in the configuration block, then run: dub -ctesting test https://dub.pm/package-format-json.html#configurations |
Copyright © 1999-2021 by the D Language Foundation