Both do some nontrivial work on DLL initialization, and conhost may quite likely never need to display UI.
Signed-off-by: Zebediah Figura z.figura12@gmail.com --- Actually gdi32 initialization is quite cheap now, at least on my machine, though user32 still takes over 100 ms. In truth the annoyance for me was not so much startup time as pollution of +server logs.
programs/conhost/Makefile.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/programs/conhost/Makefile.in b/programs/conhost/Makefile.in index fb345caba41..3ce5cee7bc9 100644 --- a/programs/conhost/Makefile.in +++ b/programs/conhost/Makefile.in @@ -1,6 +1,6 @@ MODULE = conhost.exe -IMPORTS = user32 gdi32 advapi32 -DELAYIMPORTS = comctl32 +IMPORTS = advapi32 +DELAYIMPORTS = comctl32 gdi32 user32
EXTRADLLFLAGS = -mwindows -municode -mno-cygwin
Hi Zebediah,
On 13.02.2021 00:23, Zebediah Figura wrote:
Both do some nontrivial work on DLL initialization, and conhost may quite likely never need to display UI.
See bug 38640. We probably want to create a message window for Unix consoles.
Signed-off-by: Zebediah Figura z.figura12@gmail.com
Actually gdi32 initialization is quite cheap now, at least on my machine, though user32 still takes over 100 ms. In truth the annoyance for me was not so much startup time as pollution of +server logs.
Note that when you create a new console, client does not wait for that initialization, so it doesn't block client application (unless it does any ioctl that needs conhost).
Thanks,
Jacek