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

linker issue function unresolved referenced in WinMain

3 posts in this topic

Hi all,

I am starting to write a cross-platform engine in C++ using the Visual Studio 2010 Express IDE. Currently at the early stage of trying to get the project hierarchy correct etc.

Starting with windows x86 for now I have hit a linker issue that has got me stumped. Linker issues normally are a case of a lib or include file not being present or up to date, so thats the first thing I checked and everything seems to be ok to me?

The solution to the demo can be found here and it requires the windows sdk 7.1 to have been installed:
http://www.sendspace.com/file/x82ils

From my own experience I can't see where I am going wrong and I am wondering if there is some weirdness going on with WinMain and/or VS Express that would prevent the WinMain call in the application from linking to the public function CoreInit in the Core static library.

On a seperate point I would Ideally like to drop the WinMain call into the Core library rather than have platform specific stuff in the Application project. From what I have read this is possible by defining the /Entry in the VS project settings although I am not sure what this should be set as, for the Core static lib or the Application or both.

Any advice or help anyone can provide would be greatly appreciated smile.png

MarkH.

0

Share this post


Link to post
Share on other sites
[quote name='fanaticlatic' timestamp='1347135440' post='4978090']
On a seperate point I would Ideally like to drop the WinMain call into the Core library rather than have platform specific stuff in the Application project. From what I have read this is possible by defining the /Entry in the VS project settings although I am not sure what this should be set as, for the Core static lib or the Application or both.
[/quote]

Personally I think that's a bad idea. What you gain from hiding the entry points in your library is marginal at best, and disruptive at worst.

You'll be taking control away from your users. What if they don't want to instantiate your application framework at the beginning of WinMain? Then they have to modify your library.

It's also going to cause them to have to set strange linker settings on every platform in order to properly link the engine if they decide to create new projects for it manually.

Ideally your WinMain would just be something like this:

[CODE]
int APIENTRY WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
{
Application app.
app.init( hInstance, lpCmdLine );
return app.run();
}

[/CODE]
.
With perhaps platform-specific versions of Application::init.

What would you actually gain from hiding this from your users? Edited by krippy2k8
0

Share this post


Link to post
Share on other sites
I take your point, though I think hiding this from the end user is a good thing. They should only be concentrating on the application not the platform specific bits and pieces.

[quote name='krippy2k8' timestamp='1347149085' post='4978129']

What would you actually gain from hiding this from your users?
[/quote]
I could hide the platform-specific bits with some #ifdefs wrapped around the winmain and main function definitions. Though I think it would be cleaner to have the winmain and main defined within a static lib that the common runtime then calls via the /Entry option. As I say my problem is understanding what the /Entry value should be i.e. the fully qualified name or just the function name or something else and whether the /Entry option is required for both the static library Core and the Demo application?

It's all a bit of a moot point if I cant figure out this linker issue. I seem to be able to build and run ok when the definition of the CoreInit function is placed within the header file, but it fails at the linker stage when the function is defined within the source file. All in all very frustrating problem.

Thanks for your input.
0

Share this post


Link to post
Share on other sites
Hi all,

Solved the problem. By defaut VS Express sets the Core libs output directory to be "$(SolutionDir)$(Configuration)\" but as my solution is stored in the demo project it meant all the source linkage was not being picked up! Changing the output directory for all libraries to "$(ProjectDir)$(Configuration)\" got me up and running :)

Thanks all.
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