On Monday, 15 October 2018 at 07:23:07 UTC, Laurent Tréguier
wrote:
If it's about old programs, then Windows should apply their
hacks only for old executables.
It kinda does - this only applies to 32 bit exes without a
manifest resource. If you compile with -m64, it will go away, or
if you
On Sunday, 14 October 2018 at 17:49:11 UTC, Adam D. Ruppe wrote:
On Sunday, 14 October 2018 at 15:46:57 UTC, Laurent Tréguier
wrote:
Why should an OS decide whether an executable should be run
with admin privileges ? If it has to, then it's up to the
developer to explicitly ask for it...
On Sunday, 14 October 2018 at 15:46:57 UTC, Laurent Tréguier
wrote:
Why should an OS decide whether an executable should be run
with admin privileges ? If it has to, then it's up to the
developer to explicitly ask for it...
Windows supports programs written as much as 30 years ago. The
On Sunday, 14 October 2018 at 13:20:09 UTC, Adam D. Ruppe wrote:
On Sunday, 14 October 2018 at 12:16:28 UTC, spikespaz wrote:
I'm compiling an executable that does not need administrator
privileges. For some reason though, LDC thinks it does and
marks it as elevated.
This has nothing to do
On Sunday, 14 October 2018 at 12:16:28 UTC, spikespaz wrote:
I'm compiling an executable that does not need administrator
privileges. For some reason though, LDC thinks it does and
marks it as elevated.
This has nothing to do with ldc. It is just any 32 bit program
called setup.exe or
I'm compiling an executable that does not need administrator
privileges. For some reason though, LDC thinks it does and marks
it as elevated.
=
ldc2 source\setup.d -i -I source -J build\vars -of
build\bin\setup.exe -m32 -g
=
No clue
