STDOUT (was Re: Beeps and bells.)

Why is it that SDL programs ALWAYS create stdout.txt and stderr.txt? Is it
not possible to create a console program to see this on-screen?–

Olivier A. Dagenais - Software Architect and Developer

“Lee Haywood” wrote in message
news:984342484 at ksl.uk

On 11 Mar 2001 16:17:53 +0000, Lee Haywood wrote:

We’ve had a thread about using the PC speaker recently, and David
posted a

“speaker emulator”.

But what my users want is a simple beep when using a machine without a
soundcard. I might be able to get X to give me beeps, but is there
some

simple way to get Windows to generate them (cross-compiled in Linux)?

Julian Peterson wrote:

printf("\a"); ?

Funny, but I asked for something that would work in Windows - if you do
that you’d get an entry in ‘stdout.txt’, not to a terminal.

Even in Linux it would only work if a terminal (e.g. xterm) was available
and remained available.

Ta.

  • Deth -

Why is it that SDL programs ALWAYS create stdout.txt and stderr.txt? Is
it
not possible to create a console program to see this on-screen?

Yes, just create a console program. :stuck_out_tongue:

You could, for example, change /subsystem:windows to /subsystem:console in
MSVC.

Oh, how silly. I didn’t think that option made any difference since we were
linking to sdlmain.lib and it replaced the main()…–

Olivier A. Dagenais - Software Architect and Developer

Why is it that SDL programs ALWAYS create stdout.txt and stderr.txt? Is
it
not possible to create a console program to see this on-screen?

Yes, just create a console program. :stuck_out_tongue:

You could, for example, change /subsystem:windows to /subsystem:console in
MSVC.