• 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
Servant of the Lord

Static library undefined reference to global or function

6 posts in this topic

I'm splitting my game into several static libraries for easier use.

I have my Common library, my Engine library, and my Game executable.

 

I've worked hard in the past to remove all globals, but I still have six of them and it'll really be a nuisance to get rid of them.

As an example, one of the globals is a PathResolver that helps resolve magic variables in path names ("%SCRIPTS%/myFolder/myScript.scr") and relative filepaths (making a path relative to something other than the executable). I don't want to pass it in as a parameter to every function that requires it.

 

Since Common.lib and Engine.lib are both static, and Game directly uses both, and Engine directly uses Common, so Engine link to Common or should Game or both?

 

Engine -lCommon

Game -lEngine -lCommon (Common is linked twice - is that the correct way?)

 

I've been encountering some 'undefined reference to...' the global variables. Engine and Common both compile fine, but when Game is compiled, it says 'undefined reference to' the global variable in Common that Engine and Game are both using.

 

It says the error is occurring in the Engine library, "libEngine.a(ApplicationStructure.o):ApplicationStructure.cpp:(.text+0x7d9)"

What's weird is that ApplicationStructure.cpp doesn't even use the global.

 

It also says, "......./mingw32/bin/ld.exe: ...../libEngine.a(ApplicationStructure.o): bad reloc address 0x2c in section `.rdata'"

 

So anyway, I figured that the global variables might be getting stripped out of the libraries. Do I have to export them in some way other than just labelling them as 'extern'? Bear in mind it's a static library - all my other classes and functions I'm not exporting... am I supposed to export them?.

 

Since I thought the globals might be getting stripped out (from trying to research online), I tried to wrap them in functions, and created a function called GetAppDetailsPointer() for one of the globals. Now it says that there is an undefined reference to that function.

 

Any ideas?

0

Share this post


Link to post
Share on other sites

Ah, but ofcourse! I had forgotten that libraries that depend on other libraries must be linked *before* their dependencies are linked. happy.png

I even had a comment two lines above my dependencies to remind me of that. dry.png

 

I'm assuming that I don't need to link Engine to Common, because it already #includes all that it needs to include, and will find the missing variables and functions when Engine and Common are both linked to the executable.

Edited by Servant of the Lord
0

Share this post


Link to post
Share on other sites

I'm assuming that I don't need to link Engine to Common, because it already #includes all that it needs to include, and will find the missing variables and functions when Engine and Common are both linked to the executable.

That's correct, yes (though it has less to do with #includes and more about how the linker resolves symbols). The real fun comes if Common ever needs to link to Engine, and then you have to either link to Engine when you build Common, or specify Engine twice when building Game (once before Common and once after).
0

Share this post


Link to post
Share on other sites

*snip*

I always forget about start/end-group. Thanks for reminding me!
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