• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Drakkcon

How do I keep SDL from outputting stdout to a file?

14 posts in this topic

I want to use SDL functions in my program, but I also want to be able to use the Command Prompt. Could someone tell me how to allow stdio to use the console window?
0

Share this post


Link to post
Share on other sites
Hmm, right now I dont have access to a compiler or I would test this:

in the SDL source code:

#ifndef NO_STDIO_REDIRECT

So maybe you can:

#define NO_STDIO_REDIRECT


Then again, this may be something you have to do when you compile SDL.

I hope this helps.

p.s. in linux it is pretty easy if I remember correctly using close(stdout); and then opening it with 0 I think.

On windows I am not sure.
0

Share this post


Link to post
Share on other sites
Does this have anything to do with input/ and output?because in allegro you can't really do use allegro functions in a console window so thats probable the same thing with SDL not sure so don't flame if I'am wrong.
0

Share this post


Link to post
Share on other sites
Well I installed dev-cpp on this computer and the define didnt work :(

So I was thinking I would be clever..

FILE* oldStdout;
*oldStdout = *stdout; //causes the application to crash :(

SDL_Init(....)

.....

fclose(stdout);
*stdout = *oldStdout;



I thought for sure this would work... alas, I was wrong.

If you are using windows, microsoft claims:
STDOUT 1 Output to the Command Prompt window source

If you find an answer let me know :)

If I think of anything else I will give it a try.
0

Share this post


Link to post
Share on other sites
Ugh. Nothing yet, I really wish there was something in the SDL documentation. Thanks for the help to far though, I'm going to look some more through the SDL header files.
0

Share this post


Link to post
Share on other sites
Look into your project option.

Try playing with the option in either General tab's or the Compiler\Linker.

Warlockzzz
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Drakkcon
Could someone tell me how to allow stdio to use the console window?

It's platform specific, so the following is Windows only.

  1. Create a new console window if your app is a "Win32 Application." AllocConsole is the API you want.

  2. Once you have your console, retrieve its standard input (or, possibly in the future, standard output) stream handle. You want GetStdHandle.

  3. You then want to get a C file descriptor corresponding to said handle. Windows provides the _open_osfhandle API for exactly this purpose.

  4. Now retrieve a FILE * for that file descriptor: call _fdopen.

  5. Finally, redirect the standard I/O stream pointer with code like the following:
    *stdin = *conin;
    *stdout = *conout;
    where conin and conout are the FILE *s that correspond to the input and output handles of your console, respectively.

  6. One extra step is to eliminate I/O buffering, so any data printed to stdout shows up immediately (if you want). Call setvbuf with the appropriate parameters.


You can save a lot of time by analyzing and copying the relevant bits of code from this excellent article.

Alternatively, if you're up to rebuilding SDL entirely, pass --disable-stdio-redirect as a compilation parameter.

Happy hacking.
0

Share this post


Link to post
Share on other sites
Sorry about the cross-post Oluseyi. It was before I we got your answer. I thought someone in that group might have a good idea.
0

Share this post


Link to post
Share on other sites

void ActivateConsole()
{
AllocConsole();

HANDLE newConsoleInput = GetStdHandle(STD_INPUT_HANDLE);
HANDLE newConsoleOutput = GetStdHandle(STD_OUTPUT_HANDLE);

int inFd = _open_osfhandle((long)newConsoleInput, _O_TEXT);
int outFd = _open_osfhandle((long)newConsoleOutput, _O_TEXT);

FILE* consoleIn = _fdopen(inFd, "r");
FILE* consoleOut = _fdopen(outFd, "w");

setvbuf(consoleIn, NULL, _IONBF, 0);
setvbuf(consoleOut, NULL, _IONBF, 0);

*stdin = *consoleIn;
*stdout = *consoleOut;
}



Here's my console activation function. The only problem is, I still don't get a console [sad]. What I'm probably doing wrong involves HANDLEs probably, since I don't know what a handle is a typedef of. when I use _open_osfhandle(newConsoleInput, _0_TEXT); I get an error: invalid conversion from `void*' to `long int'. I have tried casting it to many things.

Any ideas?
0

Share this post


Link to post
Share on other sites
Ah, nevermind! I fixed it, I was forgetting to call my ActivateConsole() function.

Me <--- Embarresed.

Thanks a lot oluseyi, it works!

PS: What is a file descriptor?
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0