|
|
Albrecht Schlosser schrieb am Montag, 24. April 2023 um 15:17:42 UTC+2:
On 4/24/23 12:54 imacarthur wrote:
On mingw systems that do not have editbin, we just end up
with a "fluid-cmd.exe" that is actually a Windows subsystem app,
but that's OK because under mnigw / Msys that just works
anyway...
When I added 'fluid-cmd' I wondered if we needed this for all
Windows builds or only for MSVC but I decided to build
it for all Windows builds, just in case (later this was copied by
Matt for fltk-options). If we can reduce the build of the
'*-cmd.exe' to just linking it's even less important to consider if
we could avoid building these for MinGW etc..
I am confused. So under mingw, "fluid-cmd.exe" is a Windows subsystem app, but it still provides stdout and stderr output? I thought that the whole subsystem trouble is at run time and caused by the OS rather than the build system or shell?
Also, if we stop providing fluid-cmd on mingw machines, existing build setups may still rely on its existence, right?
--
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 fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/4b5513a0-bc12-4101-8736-4a11a498ff66n%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |