• 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
viper110110

Including a c file

7 posts in this topic

From my other thread about loading PNGs, I ended up choosing a library that was distributed as a single C file (stb_image.c). What is the proper way to include this into my project and make it compile? I brought it in with an #include, but it gave duplicate definition errors because it was also compiling the file on its own. Is there a flag I can set on the file to not compile it? Or is there a better way to do it?

0

Share this post


Link to post
Share on other sites

You don't need to #include the C file itself. Treat it as you would any C file in your project. Add it to your IDE project, preferably in the same directory tree as your own source files, make sure the header file is in on your include path, #include the header in any source module in which you want to use it, and compile.
 

Sorry for the noise. I assumed incorrectly there was an associated header file.

Edited by Aldacron
1

Share this post


Link to post
Share on other sites

Try adding guard statements since your C file doesn't have a header:

 

#ifndef STB_IMAGE_C
#define STB_IMAGE_C
/* All STB_IMAGE_C code */
#endif
1

Share this post


Link to post
Share on other sites

Is there a flag I can set on the file to not compile it? Or is there a better way to do it?

Remove the file from the project, and include it -- you can include files that aren't necessarily included in the project.

Alternatively, you can include the c file in your project, and create a header file exposing a handful of pertinent functions...
0

Share this post


Link to post
Share on other sites

Looking at the file in question and comments like "end of header file" suggest that the author dumped the .h and .c into a single file for... download convenience? Laziness? Lack of a zip tool?

 

The "clean" way is to split the file into a header and a source file. If you just want to #include the whole thing, make sure there is never ever more than a single .c/.cpp file that does so.

0

Share this post


Link to post
Share on other sites

Assuming the file came from here, you're supposed to define STBI_HEADER_FILE_ONLY before including the source file like a "header" file, and then simple add the .c file to your project. I personally think it's a stupid setup, but oh well. For example:

 

YourFile.h

 

// Each file that depends on stb_img.c can "properly" include like this:
#define STBI_HEADER_FILE_ONLY
#include "stb_img.c"
 
// blah blah blah...

 

Then simply add stb_img.c to your project.

Thanks, I think I'll use this approach.

 

I found an option to just not build the C file, but as someone pointed out above, it would still fail if I include it more than once.

 

If I'm feeling ambitious, which I probably won't be, I'll make a header file and do it properly.

0

Share this post


Link to post
Share on other sites

Assuming the file came from here, you're supposed to define STBI_HEADER_FILE_ONLY before including the source file like a "header" file, and then simple add the .c file to your project. I personally think it's a stupid setup, but oh well. For example:
 
YourFile.h

// Each file that depends on stb_img.c can "properly" include like this:
#define STBI_HEADER_FILE_ONLY
#include "stb_img.c"
 
// blah blah blah...
 
Then simply add stb_img.c to your project.


this isn't entirely atypical for "single file whatever" style things.

it is a tradeoff though, like either it is something like this, or distributing the code as multiple files (or as a more conventional library).

another issue is maintainability, as a single giant source file becomes a mess to work on (in this case, placing a practical limit on how much can be done in a single source file).

some libraries "solve" this problem by then developing the library as multiple files, and then bundling them into a single giant C file for sake of other people using them in the project (hey, random programmer, how do you feel about a 4MB C source file?...). (side note: SQLite...).


well, it is either this, or expect people to be able to figure out how to use multiple files, or make it a traditional library (and deal more with the matter of different compilers and build targets), ... (and sometimes people who get really annoying and whine in terror that getting their stuff to build might happen to involve having to edit or customize a Makefile and/or figure out how to include all the files into a VS project or similar, or start playing the blame game and making a huge fuss about whose responsibility it is to make sure the code works on their target OS/compiler/... of choice, ...). (vs people taking it on themselves to edit the code and makefiles to work on their target of choice if they feel so inclined... like FFS they are getting the code for free...).
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