Re: [fltk/fltk] windows+fltk1.3.x+1.4.x: "fluid -c somefile.fl" fails without error if .fl file unreadable (#224)

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.issues  ]
Previous Message ]New Message | Reply ]Next Message ]

Re: [fltk/fltk] windows+fltk1.3.x+1.4.x: "fluid -c somefile.fl" fails without error if .fl file unreadable (#224) Albrecht Schlosser Apr 27, 2021 top right image

I'm pretty sure ANY windows builds are affected, as this is an OS level thing. Which is to say even mingw, which has a slightly differently named flag (-console?), but has the same effect IIRC.

This would be -mwindows and -mconsole IIRC. I noticed a different behavior when I ran the GUI version of fluid in a MinGW shell though: stdout seemed to work which surprised me.

But I agree that it would make sense to build two executables for all Windows builds.

I think fluid-cmd would be clearer; this is what I've seen other commercial apps do that run into the same problem, and I've used it too.

No problem, fine for me. Side note: the FLTK docs describe this backgrounding of fluid somewhere, checked yesterday, but I don't have a link.

start /WAIT fluid -c bla.fl

Oh yes, there's something in my faint Windows memory... That's probably the way CMake runs these commands, it makes sense.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

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-2022 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to ''.