Re: [fltk.coredev] What does the "fluid-cmd" exe do on the WIN32 builds?

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
Previous Message ]New Message | Reply ]Next Message ]

Re: What does the "fluid-cmd" exe do on the WIN32 builds? imm 06:24 Oct 01 top right image
On Sat, 1 Oct 2022 at 13:32, Albrecht Schlosser wrote:
> The only difference is that it's a Windows Console (-mconsole) rather
> than a Windows GUI (-mwindows) executable. This was done on request (by
> Greg) because some fluid issues (e.g. not being able to access remote
> file systems or other errors) would not display an error message if
> built as GUI exe as it was before.

Ah, OK.
Well, annoyingly, that's a "feature" of the DOS shell, that it drops
the stdio handles for GUI applications; the Msys shell does not, so
you still get stdio to the console on GUI applications, if you run
them from an Msys shell.

So I'd probably never seen the behaviour that Greg was seeing - and
conversely, he probably never sees the behaviour I see!

> > Anyway, I noticed this because a 32-bit mingw checkout choked at build for me - stuck in fluid-cmd.exe, just sitting there... indefinitely...
> Sigh. This is something I experienced as well but it is not related to
> using fluid vs. fluid-cmd. I had this issue before and after the
> modification, and it happens sometimes but not every time I build FLTK
> with MinGW (MSYS2/mingw-w64 to be precise). I wonder if it has something
> to do with virus checking (Windows Defender) but I could never find it
> out. I tried to add a Defender exception but this didn't really work. I
> can usually see lots of CPU activity related to "virus checking" or
> whatever its name is while I'm building FLTK - unless I disable online
> virus checking entirely while building FLTK. Virus checking of the FLTK
> build is a PITA anyway (steals way too much CPU time and probably also
> disk activity).

OK - well, knowing that it is not just me is useful!
If it is a virus scanner side-effect, it is not just Defender, as I
have seen the same behaviour on machines "protected" by
McAfee/Trellix/whatever-it-is-called-now too.

You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit
Direct Link to Message ]
bottom left image   bottom right image
Previous Message ]New Message | Reply ]Next Message ]

Comments are owned by the poster. All other content is copyright 1998-2023 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to ''.