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

How to statically link OpenAL-Soft for VC++

4 posts in this topic

I've been looking all over the internet for a guide to link OpenAL-Soft statically with VC++. At the moment I have it working dynamically, but all my other libraries are statically linked and it would be really nice if I could do the same with OpenAL-Soft. I keep hearing that static linking is discouraged for OpenAL-Soft due to licensing issues, but according to this post, I should be fine.

 

I was able to compile the library statically by doing "cmake -DLIBTYPE=STATIC .." and moving the generated lib file to my game's folder, but when building my program I got unresolved external symbol errors when calling OpenAL functions. I made sure that the lib was included in the VS linker settings. Not sure what to try at this point.

 

Thanks!

Edited by Petwoip
0

Share this post


Link to post
Share on other sites

May I suggest that you don't? I'll give an example specifically for openal-soft:

 

I tried to run Euro Truck Simulator 2, but it would crash immediately on startup. I remembered that this happened for one specific version of openal soft when working on my own game, so I was able to replace ETS2's dll with a newer one, which stopped the crashing. It took a few hours of reinstalling and trying everything under the sun before I realized it, but I would not have been able to play if they had linked it statically.

 

 

That said...

Compiling (which you said you did, and cmake probably did the right thing):

Go to openAL-soft's config.h (should be in the directory where the other openal projects are generated), and make AL_API and ALC_API defined as nothing. Then, go in to the OpenAL32 project in VS -> Properties -> General -> Configuration Type set to static library. Of course, do this for all release/debug/whatever else. Build OpenAL like that.

 

Linking:

In the project that you intend to statically link openAL in to, have AL_LIBTYPE_STATIC defined (Project-> Properties-> C/C++ ->Preprocessor -> Preprocessor Definitions). Found that in al.h line 9.

0

Share this post


Link to post
Share on other sites

but according to this post, I should be fine.

The information in link is a bit incorrect.

 

LGPL requires (from http://www.gnu.org/copyleft/lesser.html):

d) Do one of the following:

  • 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
  • 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.

So you are required to provide sources of your app, so users can link to different implementation of OpenAL library. Or you are required to use shared library when linking to OpenAL.

2

Share this post


Link to post
Share on other sites

Hmm, I should have investigated further... I guess I'll stick with using a shared library because I might want to keep my app closed source.

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