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

freeglut Linking error

5 posts in this topic

Hello.

Here is what I am working with.
[CODE]
#include <stdlib.h>
#include <GL/freeglut.h>
int main()
{
return 0;
}
[/CODE]

I am getting a linking error running this
[CODE]
fatal error LNK1120: 1 unresolved externals
[/CODE]

This is what I am linking using additional dependencies.
freeglut.lib;

I guess what I am trying to ask is, What do I need to link to get freeglut to work?
0

Share this post


Link to post
Share on other sites
That error is unlikely to be the only one. There will be errors above there telling you exactly which symbols are unresolved. Without knowing the symbols you cannot even be sure the problem is freeglut, it could be a dependency of freeglut or something else entirely you are not linking. Or you could be using /SUBSYSTEM:Windows in which case you need to change that or define WinMain as the entry point.
2

Share this post


Link to post
Share on other sites
[quote name='BitMaster' timestamp='1355211644' post='5009361']
That error is unlikely to be the only one. There will be errors above there telling you exactly which symbols are unresolved. Without knowing the symbols you cannot even be sure the problem is freeglut, it could be a dependency of freeglut or something else entirely you are not linking. Or you could be using /SUBSYSTEM:Windows in which case you need to change that or define WinMain as the entry point.
[/quote]

Thank you. The problem was I created a win32 application, and not a win32 console application. I have no idea why this would matter though.
0

Share this post


Link to post
Share on other sites
The entry function is the function which is called by the runtime to start the actual program after runtime initialization has finished. For /SUBSYSTEM:Console the common signatures are [code]int main();
int main(int, char**);[/code]
See the standard (or [url=http://en.wikipedia.org/wiki/Main_function#C_and_C.2B.2B]Wikipedia[/url] if a standard is not at hand) for a complete list of what is allowed here, although MSVC allows a few non-standard extensions.

For /SUBSYSTEM:Windows the entry function must be [code]int CALLBACK WinMain(HINSTANCE, HINSTANCE, LPSTR, int);[/code]
Although it is possible to change the name of the entry function in MSVC, the signature still must be as expected.
2

Share this post


Link to post
Share on other sites
[quote name='BitMaster' timestamp='1355242452' post='5009445']
The entry function is the function which is called by the runtime to start the actual program after runtime initialization has finished. For /SUBSYSTEM:Console the common signatures are [code]int main();
int main(int, char**);[/code]
See the standard (or [url="http://en.wikipedia.org/wiki/Main_function#C_and_C.2B.2B"]Wikipedia[/url] if a standard is not at hand) for a complete list of what is allowed here, although MSVC allows a few non-standard extensions.

For /SUBSYSTEM:Windows the entry function must be [code]int CALLBACK WinMain(HINSTANCE, HINSTANCE, LPSTR, int);[/code]
Although it is possible to change the name of the entry function in MSVC, the signature still must be as expected.
[/quote]

Okay your telling me about /SUBSYSTEM:Console and /SUBSYSTEM:Windows.

Are these what you are reffering to?
[img]http://s10.postimage.org/r06g92k55/inquiry.png[/img]

If so I have another question.

I created a empty project both times. So I dont see how using the [CODE]int CALLBACK WinMain(HINSTANCE, HINSTANCE, LPSTR, int);[/CODE] or using the [CODE]int main()[/CODE] would have an effect.

I did use int main() {} both times. And on seperate projects using FLTK I used int main {} as the starting point on both empty win32 application and an empty win32 console application. However all I did was write the code in main.cpp. I didn't change any options aside from adding the neccessary links to the FLTK libs.

Thanks for the explanation I appreciate it.
0

Share this post


Link to post
Share on other sites
I generally do not use the templates provided to create projects, so I cannot comment on their predefined settings. Even so, in MSVC 2008 the setting is simply accessible via Project Properties->Configuration Properties->Linker->System->SubSystem, so regardless of which template you have chosen, you can change that whenever the need arises.

Additionally, some libraries also come with an option to map the non-standard WinMain to a call to main (Qt and SFML both have an optional sublibrary to link for these cases).
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