https://issues.dlang.org/show_bug.cgi?id=20699

Hiroki Noda <kubo39@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kubo39@gmail.com

--- Comment #1 from Hiroki Noda <kubo39@gmail.com> ---
It seems dub's bug, not dmd.

Maybe related: https://github.com/dlang/dub/pull/1905

--

https://issues.dlang.org/show_bug.cgi?id=20699

kinke <kinke@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kinke@gmx.net
           Hardware|x86                         |All

--- Comment #2 from kinke <kinke@gmx.net> ---
(In reply to Hiroki Noda from comment #1)
> It seems dub's bug, not dmd.
> 
> Maybe related: https://github.com/dlang/dub/pull/1905

dub can only work around it (that PR doesn't). Fixing this for DMD makes sure no other build tools need to take this special case into account.

--

https://issues.dlang.org/show_bug.cgi?id=20699

--- Comment #3 from Hiroki Noda <kubo39@gmail.com> ---
(In reply to kinke from comment #2)
> (In reply to Hiroki Noda from comment #1)
> > It seems dub's bug, not dmd.
> > 
> > Maybe related: https://github.com/dlang/dub/pull/1905
> 
> dub can only work around it (that PR doesn't). Fixing this for DMD makes sure no other build tools need to take this special case into account.

Ah, I'm wrong. sorry.

--

https://issues.dlang.org/show_bug.cgi?id=20699

--- Comment #4 from JR <zorael@gmail.com> ---
Is there untractably much work involved?

I could really use -lowmem for CI builds where available memory is limited. Alternatively a way to programmatically get the commands dub (supposedly) performs, so I could just tack -lowmem onto there.

--

https://issues.dlang.org/show_bug.cgi?id=20699

hsteoh@qfbox.info changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsteoh@qfbox.info

--- Comment #5 from hsteoh@qfbox.info ---
Run dub with --vverbose and it should show the compile commands explicitly.

--

https://issues.dlang.org/show_bug.cgi?id=20699

--- Comment #6 from JR <zorael@gmail.com> ---
(In reply to hsteoh from comment #5)
> Run dub with --vverbose and it should show the compile commands explicitly.

This is true, but there is no --dry-run to make it only output the commands without also building the package. So I can't programmatically capture the output and grep it with a script/short program in a neat way.

Manually copy/pasting the command into a different build system (e.g. makefiles if I can get that to work) breaks as soon as a dependency is updated and its ~/.dub/packages path changes, provided I use dub for dependency management.

--

https://issues.dlang.org/show_bug.cgi?id=20699

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3

--