Thread overview
How not to run after a DUB build ?
Sep 17, 2015
BBasile
Sep 17, 2015
BBasile
Sep 18, 2015
ponce
September 17, 2015
Each time I execute

`dub.exe --build=release` (or any other the build type)

DUB tries to run the project after the build.

This generates often generates an error when dub process returns (and even if the build is OK) but actually I don't want DUB to run after building. Is there a switch to avoid the exexution after the build ?
September 17, 2015
On Thursday, 17 September 2015 at 19:36:10 UTC, BBasile wrote:
> Each time I execute
>
> `dub.exe --build=release` (or any other the build type)
>
> DUB tries to run the project after the build.
>
> This generates often generates an error when dub process returns (and even if the build is OK) but actually I don't want DUB to run after building. Is there a switch to avoid the exexution after the build ?

NVM, just get that 'build' and '--build=' are two different things.

with  `dub.exe build --build=release` nothing is executed...
September 18, 2015
On Thursday, 17 September 2015 at 19:44:36 UTC, BBasile wrote:
> On Thursday, 17 September 2015 at 19:36:10 UTC, BBasile wrote:
>> Each time I execute
>>
>> `dub.exe --build=release` (or any other the build type)
>>
>> DUB tries to run the project after the build.
>>
>> This generates often generates an error when dub process returns (and even if the build is OK) but actually I don't want DUB to run after building. Is there a switch to avoid the exexution after the build ?
>
> NVM, just get that 'build' and '--build=' are two different things.
>
> with  `dub.exe build --build=release` nothing is executed...

Yes, the default command is "dun run"