Hi, I have the following line in my dub.json file:

"libs-windows-x86_64": ["user32", "kernel32", "gdi32", "b2d_playground"]

b2d_playground is a C based .lib file. If this lib is updated and I run: dub build --arch=x86_64 nothing happens. The EXE is not rebuild, taking into accoun the updated lib file. IMO dub should re-link the EXE.

Is this by design or a bug?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

On Sunday, 1 April 2018 at 17:01:46 UTC, Robert M. Münch wrote:
> Hi, I have the following line in my dub.json file:
>
> "libs-windows-x86_64": ["user32", "kernel32", "gdi32", "b2d_playground"]
>
> b2d_playground is a C based .lib file. If this lib is updated and I run: dub build --arch=x86_64 nothing happens. The EXE is not rebuild, taking into accoun the updated lib file. IMO dub should re-link the EXE.
>
> Is this by design or a bug?

Bug. Imho dub should compare the timestamp of its dependencies and see whether they are newer than the target like e.g. Make.

https://github.com/dlang/dub/issues/new

On 2018-04-01 22:24:54 +0000, Seb said:

> Bug. Imho dub should compare the timestamp of its dependencies and see whether they are newer than the target like e.g. Make.
> 
> https://github.com/dlang/dub/issues/new

Just found out, that I had two versions of DUB installed... one very old. Going to x-check if this is still happening with newer version.

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

On Wednesday, 4 April 2018 at 13:28:39 UTC, Robert M. Münch wrote:
> On 2018-04-01 22:24:54 +0000, Seb said:
>
>> Bug. Imho dub should compare the timestamp of its dependencies and see whether they are newer than the target like e.g. Make.
>> 
>> https://github.com/dlang/dub/issues/new
>
> Just found out, that I had two versions of DUB installed... one very old. Going to x-check if this is still happening with newer version.

Else you can always force a rebuild.