Failed to compile examples using VS2013 - lib is not proper?

If you are a new Irrlicht Engine user, and have a newbie-question, this is the forum for you. You may also post general programming questions here.
Post Reply
fargoth
Posts: 22
Joined: Fri May 01, 2015 7:43 pm

Failed to compile examples using VS2013 - lib is not proper?

Post by fargoth »

I'm trying to compile Irrlicht 1.8.1 using the "buildallexamples" solution.
I've opened the vc11 and converted it successfully.
I've successfully told it to not compile DX8 and DX9.
The Irrlicht project compiles alright - but in the debug or release configuration it does not create a .lib file - just a .dll in the bin folder.
If I change the configuration to static lib - and than it does create a .lib file.
The problem is that all the examples fail to link, complaining about createDevice external symbol not being found...
I've made sure the lib directory is correct in all these projects...
Maybe the signature is somehow wrong in the lib file? Anyone has Ideas?

Thanks.
Foaly
Posts: 142
Joined: Tue Apr 15, 2014 8:45 am
Location: Germany

Re: Failed to compile examples using VS2013 - lib is not pro

Post by Foaly »

As far as I know, there is an extra lib folder, so the .lib file will be there and not in the bin folder.
fargoth
Posts: 22
Joined: Fri May 01, 2015 7:43 pm

Re: Failed to compile examples using VS2013 - lib is not pro

Post by fargoth »

I've looked there...
In debug or release configuration the .lib file is not present in the lib folder, and the dll is created in the bin folder (but VS reports build is successful)
And in Static lib debug or static lib release configuration the .lib file is created in the lib folder - but the other examples (which look for it in the correct place and seem to find it) fail to find the external symbol createDevice....
fargoth
Posts: 22
Joined: Fri May 01, 2015 7:43 pm

Re: Failed to compile examples using VS2013 - lib is not pro

Post by fargoth »

Ok, I don't know exactly what was wrong - but I've changed the directories of the place it should put the lib for the release and debug configurations - now the lib is created along with the dll, and the examples can link against the lib...
One of those weird visual studio quirks I guess...
Post Reply