Thread overview |
---|
September 17, 2015 How not to run after a DUB build ? | ||||
---|---|---|---|---|
| ||||
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 Re: How not to run after a DUB build ? | ||||
---|---|---|---|---|
| ||||
Posted in reply to BBasile | 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 Re: How not to run after a DUB build ? | ||||
---|---|---|---|---|
| ||||
Posted in reply to BBasile | 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"
|
Copyright © 1999-2021 by the D Language Foundation