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

GLEW Linker Error/Check Extension Support at Compile Time?

2 posts in this topic

Hi,

 

I am trying to compile and run some of my new code on my old laptop. My current code was developed on a GL 4-capable machine, and uses several key extensions that are not supported on the older device.

 

When building on the newer machine, it works perfectly. When building on the older machine, despite a nearly identical build chain, it fails with linker errors. Specifically, some GLEW functions are referenced as undefined. I am linking against the library, in the same place as the working build, and, incidentally, last in the linker order. The undefined functions include __glewUniform1D and __glewBindImageTextureEXT. Such functions come from extensions (in those cases, GL_ARB_gpu_shader_fp64 and GL_ARB_shader_image_load_store, repsectively)--notably extensions that the older laptop doesn't list as supported.

 

I have an extremely fuzzy conception of how GLEW actually works, but since other GLEW functions (e.g. glewInit) are not listed as undefined, I draw the conclusion that perhaps the extensions don't exist and so can't be linked to. Though, since the library versions of GLEW are the same (1.5) and I can't think of a mechanism besides, I can't be sure.

 

However, it also gives rise to another idea. Since the extensions aren't supported anyway, it would be convenient to be able to remove code that won't work at compile time. Though, since GPU detection, I expect, can only be done at runtime, I don't see how that could work.

 

So: why the linker errors? And, can extensions be checked at compile-time?

 

Thanks,

-G

0

Share this post


Link to post
Share on other sites
It's unclear to me why you have linker errors. The point of GLEW is that it retrieves the extension support of the system it's currently running on - the capabilities of the system it was originally compiled on should not matter at all. You should investigate what "nearly identical build chain" means, especially the part 'nearly'. 
 
Considering that GLEW 1.5 is more than five years old, you might want to investigate a newer version, even if you do not need support for newer extensions.
 
Also take a close look at how you built GLEW for both platforms.
 
If you are linking GLEW statically, doublecheck that GLEW_STATIC is defined everywhere where GLEW is included.

Are there any warnings apart from the errors?
0

Share this post


Link to post
Share on other sites

It's unclear to me why you have linker errors. The point of GLEW is that it retrieves the extension support of the system it's currently running on - the capabilities of the system it was originally compiled on should not matter at all. You should investigate what "nearly identical build chain" means, especially the part 'nearly'.

I mean, insomuch as they can be on different computers and OSes (Ubuntu 10.04 versus 12.04). The sources are the same, the cmake files are the same, except for one flag which just changes where it finds my libraries.
 

Considering that GLEW 1.5 is more than five years old, you might want to investigate a newer version, even if you do not need support for newer extensions.

I think I was mistaken when I said the GLEW versions are the same. They are both the latest available for their respective platforms, but that's 1.5 versus 1.6.
 

Also take a close look at how you built GLEW for both platforms.

Good plan.
 

If you are linking GLEW statically, doublecheck that GLEW_STATIC is defined everywhere where GLEW is included.

I am, they are.
 

Are there any warnings apart from the errors?

No.

I believe the problem was due to the GLEW version. I updating the older OS to 13.04, and got the newer version of GLEW the linker errors disappeared.

Thanks,

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