Emit notice when compiling with -release - #124
Conversation
|
sooooooo druntime uses it in the build. i guess kidna harmless but maybe it should be updated |
|
I know it’s tiring, but please review these substitutions. I’ve staged them patch by patch but it is easy to miss a case where |
|
3ddd480 is untested. |
|
actually i might have made a mistake in requesting that cuz it bootstrap builds w/ upstream....... ugh |
|
so yeah sorry for making you do something tedious and useless but it should prolly just keep using -release for compatibility with upstream host compilers doing the build, the message is ok to see anyway tbh |
No big deal, running |
But doesn’t it use the fresh DMD to build druntime + Phobos? |
|
oh, |
3ddd480 to
818adf6
Compare
|
I think this should work fine now. |
|
well let's try it and see lol |
|
yea it failed so ima undo the changes to the build scripts |
|
actually it isn't the build script, it is the ldc commit saying redefinition. megannoying template magic |
|
or actually maybe just a reused variable lemme try changing that |
|
awesome, thanks ^^ |
Partially revamps ldc-developers/ldc#4739 — but for DMD.
Using
-ludicrousinstead of-releasegets one rid of the notice message.