Sign in to follow this  
phil67rpg

openAL sound init

Recommended Posts

phil67rpg    443

I am getting the following error with the alutInit(0,NULL); command.

here is the error I am getting

Error 18 error LNK2019: unresolved external symbol _alutInit referenced in function _main C:\Users\Phillip\Documents\Visual Studio 2012\Projects\texture\texture\main.obj texture
 

Share this post


Link to post
Share on other sites
Khatharr    8812

"unresolved external symbol" means that the linker sees a call to function that was prototyped but it can't find the place where the function was defined. Try a full rebuild and see if that clears it up. Otherwise there's something wrong in your linkages and we'll need to take a closer look.

Share this post


Link to post
Share on other sites
EddieV223    1839

Your libs are not setup right.  Make sure you have the proper libs for your platform, including the os, the 32/64 bit libs, and static/dynamic libs, as well as any preprocessor definitions you may need ( these instruct the libs how to behave ).

Share this post


Link to post
Share on other sites
EddieV223    1839

What ever lib alutInit() is in is not setup right.

 

Looks like from googling that you need a seperate lib for this, its ALUT.

 

Get it here 

 

http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx?RootFolder=%2fopenal%2fDownloads%2fALUT&FolderCTID=&View=%7b6A9700C6-7248-4CD2-83F5-268F2C176072%7d

Edited by EddieV223

Share this post


Link to post
Share on other sites
FLeBlanc    3141
This kind of link problem typically occurs when the DLL that your program linked against is different from the DLL that it is trying to hook up to at run-time. At link time, the application was essentially told " this procedure will be located at this location in the DLL, so when you run look for it there." But at run-time, the loaded DLL is differently laid-out, so when the application goes to look where it was told it can't find it. This can occur from using different versions of a library, using a library built on a different version of the compiler, etc... There isn't really any kind of quick "this is what you do to fix it" solution, which is why you aren't really getting any answers here

Sometimes, you can run into a problem of DLL "shadowing", where you have 2 different versions of a DLL in your path chain, and while you might have a correct DLL in one place that you expect the program to find, another one higher up the search chain might be grabbed instead, resulting in a link error.

Go through your paths, make sure there aren't multiple versions of the DLL available. Make sure that you are linking against the correct version of your DLL. If all else fails, a clean rebuild of your library might help to resolve the issue. You can use a tool like Dependency Walker to analyze your .EXE and see what DLLs it is dependent upon, and make sure that the proper versions of those DLLs are located where the program can find them.

Share this post


Link to post
Share on other sites
phil67rpg    443

Sometimes, you can run into a problem of DLL "shadowing", where you have 2 different versions of a DLL in your path chain, and while you might have a correct DLL in one place that you expect the program to find, another one higher up the search chain might be grabbed instead, resulting in a link error.

how do I access the path chain using vs2012

Share this post


Link to post
Share on other sites
FLeBlanc    3141
You don't need VS2010. Just look in all the places that Windows will search for DLLs, and make sure you don't have an extra DLL somewhere that shouldn't be there. This includes the execution directory, the active directory, the windows system directory, the windows directory, and any directory listed in your PATH environment variable.

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