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

Error when compiling SuperBible samples on mac OSX

3 posts in this topic

Hello,

As the title says, I'm trying to compile the samples from the blue superbible on mac, but I get some Linker errors. 27 errors:

Undefined symbols for architecture x86_64:
  "sb6IsExtensionSupported(char const*)", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "sb6::application::app", referenced from:
      sb6::application::run(sb6::application*) in main.o
      sb6::application::glfw_onResize(int, int) in main.o
      sb6::application::glfw_onKey(int, int) in main.o
      sb6::application::glfw_onMouseButton(int, int) in main.o
      sb6::application::glfw_onMouseMove(int, int) in main.o
      sb6::application::glfw_onMouseWheel(int) in main.o
  "_gl3wClearBufferfv", referenced from:
      MyApplication::render(double) in main.o
  "_gl3wDebugMessageCallback", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wDebugMessageCallbackARB", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wEnable", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wInit", referenced from:

Any idea on how I should resolve this ?

 

Thanks :)

0

Share this post


Link to post
Share on other sites

Unresolved symbols complaints from the linker almost certainly means that your linker can't find the library for GLFW.  I did answer to a similar thread yesterday where I explained the same, but for a different library.  Luckily for you, I am using GLFW myself in one of my projects.

 

Here is the link to the thread:

http://www.gamedev.net/topic/659083-xcode-cant-find-freeglut/

 

While the question in the thread really is for freeglut, my answer was how GLFW is installed on my machine.  It should be almost the same.  (Given that you have installed GLFW in the same location as me - my installation was pretty much default, so it should work.)

 

Not sure which version you are using, but if you search for the file 'libglfw.3.0.dylib' (with correct version number), you know which folder to put.

 

Here is a screen shot that will help a bit more:

 

glfwlib.png

Edited by aregee
0

Share this post


Link to post
Share on other sites

What is strange, is that I've correctly link to the lib folder that contains the .dylib, so what I've finaly done is to drag and drope the .dylib file in XCode manually and some errors disappeared. But I have always 9 errors beacause of gl3w...

 

Undefined symbols for architecture x86_64:
  "sb6IsExtensionSupported(char const*)", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "sb6::application::app", referenced from:
      sb6::application::run(sb6::application*) in main.o
      sb6::application::glfw_onResize(int, int) in main.o
      sb6::application::glfw_onKey(int, int) in main.o
      sb6::application::glfw_onMouseButton(int, int) in main.o
      sb6::application::glfw_onMouseMove(int, int) in main.o
      sb6::application::glfw_onMouseWheel(int) in main.o
  "_gl3wClearBufferfv", referenced from:
      MyApplication::render(double) in main.o
  "_gl3wDebugMessageCallback", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wDebugMessageCallbackARB", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wEnable", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wInit", referenced from:
      sb6::application::run(sb6::application*) in main.o
  "_gl3wIsSupported", referenced from:
      sb6::application::run(sb6::application*) in main.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
 

0

Share this post


Link to post
Share on other sites

I wrote the second part first, but thought maybe the first part were worth a try:

 

1.

Reading around, I see suggestions that the problem may be that you didn't compile GLFW for the right target (see the 'Undefined symbols for architecture x86_64'), that might be your problem, but I can't tell that for sure.

 

Other than that, this really should work:

 

2.

Yes, when you dragged the dylib file into the project, you probably added it into "Frameworks"?  You could try to remove (not delete unless it is a copy of the dylib located in your project folder) from the project, and add it as I am describing in point 1 below.

 

Doing all three below should be enough to make the project work:

 

1. Adding the Framework

 

This was a bit of hassle, if I remember correctly.  The problem was to access the hidden folders that the library is located in.  In the file open dialog when adding frameworks, you can press SHIFT + CMD + G, and it will pop up the "Go to folder..." dialog box, and you can manually enter the path to the dylib file.  (It is a dylib file in my Framework "group folder", not sure why you need to specify that when you add the path to the library files, or vice versa...)

 

2. Adding a path to the include files

3. Adding a path to the library file(s)

 

Those three things, of course after having compiled GLFW, but I assume you have done that already, since you have a dylib file to start with.

Edited by aregee
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