|
|
On 4/25/23 08:24, imacarthur wrote:
I'd assume Greg uses it in his Windows builds, for example?
Ya, I need to be able to generate executables via makefiles
that detect
failures from fluid via exit codes; Windows apps invoked from
a Makefile
immediately run 'in the background' and don't ever return exit
codes
indicating failures from code generation (-c flag).
Also, on headless machines there's no way to see the record of
failure
in the error logs of non-console apps. For instance a
permission problem
reading the .fl file, or a write problem for the .cxx/.h files
due to
code directory permissions or network file access issues.
--
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/474f77f0-8069-1e55-a61f-f7ce36fda4b9%40seriss.com.
[ Direct Link to Message ] | |
|
| |