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

Archived

This topic is now archived and is closed to further replies.

wing_majin

error including the damn libraries wtf?

7 posts in this topic

*anger* I can't begin to say how much long i've dealt with this.... I'm trying to make some standard classes for my own use in GL. I write all my classes fine etc etc, nothing complicated as such to induce any errors. However as soon as I include JUST like the pros do in their source (ex NeHe etc) I get a wondeful trio of compiling errors telling me basically that things are either getting redefined or who knows etc etc. This occurs as soon as I include it AND when there's a file in it I downloaded as a tutorial or something that has the EXACT same thing "#include " as my own class..... c:\program files\include\gl\gl.h(1152) : error C2144: syntax error : missing ';' before type 'void' c:\program files\include\gl\gl.h(1152) : error C2501: 'WINGDIAPI' : missing storage-class or type specifiers c:\program files\include\gl\gl.h(1152) : fatal error C1004: unexpected end of file found (and those errors all occur, supposadly, IN gl/gl.h ) Is there something up with my project settings? Edited by - wing_majin on October 25, 2001 2:02:41 AM
0

Share this post


Link to post
Share on other sites
Those errors arent from including the libraries, rather the header files.

Make sure all the lines BEFORE you #include gl/gl.h are correct (ie not missing semi-colons, etc)
0

Share this post


Link to post
Share on other sites
Yeah I''m aware that it''s the file, and although it seems like those are common "human screw up" errors...
#include is the absolute first line in the file
so i figured it might have somethign to do with my settings somwhere im not sure
0

Share this post


Link to post
Share on other sites
If the #include ... is in the first line of your header files, maybe that's the cause for the errors. If your #includes are in a header file you wrote yourself, make sure you have an #ifndef ... #define ... #endif construct in your own header files.

Example:

// myheader.h
#ifndef _MYHEADER_H_
#define _MYHEADER_H_

#include <gl/gl.h>
#include <gl/glu.h>

... declarations ...

#endif // #ifndef _MYHEADER_H_
// end of myheader.h


baumep

Edited by - baumep on October 25, 2001 2:54:53 AM
0

Share this post


Link to post
Share on other sites
Thanks, but yeah, I know how to write and define classes and all that and im fairly aware of the whole linking process. However, I DO have all that there, but I require the GL in my implementation file "header.cpp", when I include that with a nicely defined class...it gives problems
0

Share this post


Link to post
Share on other sites
What happens is that WINGDIAPI class is undefined, so the when the complier sees
WINGDIAPI void APIENTRY glAccum (GLenum op, GLfloat value);
- the first function prototype in the header file, it doesn''t know what WINGDIAPI is, so you get the error '';'' missing before type ''void''

All you have to do is what siaspete said #include before #include and you''ll be fine.
0

Share this post


Link to post
Share on other sites
Thanks that did it. I figured it had something to do with definition here or there but I didn''t think it was that simple to fix
0

Share this post


Link to post
Share on other sites