• BBasile (7/7) Sep 17 2015 Each time I execute
• BBasile (4/11) Sep 17 2015 NVM, just get that 'build' and '--build=' are two different
• ponce (2/16) Sep 18 2015 Yes, the default command is "dun run"

BBasile <bb.temp gmx.com> writes:

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 ?

BBasile <bb.temp gmx.com> writes:

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...

ponce <contact gam3sfrommars.fr> writes:

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"