Update of bug #30489 (project gnustep):
Status: Works For Me => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #5:
I'll close this as what we are talking about now is not an NSLog() issue, but
rather an issue of where stdout and stderr go to on mswindows.
If you search for information about mswindows handling of stdin/stdout on the
net you will find that a binary can be marked to use a different I/O
subsystem, and the 'editbin' tool can be used to change the setting for a
particular binary (so you could probably use this program to get the behavior
you want). If you want to send stdout and stderr to the windows console, you
likely need to mark your binary as using the CONSOLE subsystem, or add code to
open and use a console directly.
I guess you could make an argument for having gnustep-make link the program
the 'right' way (ie explicitly link a 'tool' one way and link an 'app' another
way) ... IMO that ought to be done as a change request for gnustep-make (and I
expect Nicola would be grateful if you could find out exactly what linker
options are needed to control this).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30489>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
