Separate names with a comma.
Discussion in '3DS - Homebrew Development and Emulators' started by DarkFlare69, Dec 17, 2014.
I have the file, where do I put it? Assets folder? Build folder? Where?
I'm a bit confused, why do you want a single header file? Just use the standard methods currently provided. I don't think putting conio.h anywhere is going to make it work.
Edit: Memory is coming back to me now, there is no reason to use this on the 3DS, or ever at all. It's an old deprecated library.
I might be doing old school C or something... but how do you print a message using C? The way I remember required conio.h
that only ever worked on windows and isn't even used to print text, it's used to control where in a cmd window to draw text, graphical style. Look at ctrulib because there is no standardized way to do this cross-platform.
That you even need to ask where to put a header file shows that you need to go and read up on some C and/or C++ then come back and read up on 3DS HB development to finally get developing
(header-files is C/C++ development 101 )
I think they go in the data folder with main.c
.c/.cpp files are source files and should be placed in the "source" folder. Please read a bit of C/C++ before attempting to develop homebrew
Conio.h is an ooooold Windows header file that won't work. Why are you using it? Are you reading a book that recommends it?
ok ill read some later
how to i #include <> a whole directory? or can it only be indiviual files at once
From the sort of questions you're asking it's obvious you're just getting started with C programming. Trying to write for the 3DS will probably just confuse you more than help you. If you tell us how you're learning C ie. books or websites we can probably help you find better resources to help you learn.
im trying to use websites. but heres the thing, i havent really bothered to try learning it much because there's no telling when fucking command line will let me make a file or give me errors. it pisses me off.
The starting point is usually a book or real world class, and they would cover that there, after which you can explore on your own using the internet.
Having said that, you can stick the online examples into Visual Studio Community Edition, Dev-C++, Code::Blocks, or any other IDE. Just make a project in them and add the code. The complexities of dealing with makefiles are best left for once you have a better grasp of C or C++, whichever you decided to pick. That's my 2ct anyway.
I personally like Dev-C++ on windows because it's very basic and allows you to easy use makefiles if you choose to, or any other compiler options.