- Forum
- General C++ Programming
- Using the SOIL library
Using the SOIL library
I'm having the same problem that this person: http://www.gamedev.net/topic/590453-opengl-soil-library-not-compiling/ is having, but I didn't follow the explanation of the solution as I've never had to deal with anything such as this before. If anyone could offer advice, it would be much appreciated.
On a side note, the official SOIL website can be found here: http://www.lonesock.net/soil.html
I am also using VSE2010.
On a side note, the official SOIL website can be found here: http://www.lonesock.net/soil.html
I am also using VSE2010.
Last edited on
The library file available there is for MinGW. It can be made to link with VC++ binaries, but it's... messy. You should try building the code from source.
closed account (236Rko23)
care to explain better? what errors are u getting? have u tried to compile from source as the guy says?
like u don't even say what your problem is. If it's that it's not compiling it can be a hell of a lot of causes, from missing libraries, to misconfiguration.
like u don't even say what your problem is. If it's that it's not compiling it can be a hell of a lot of causes, from missing libraries, to misconfiguration.
I'm getting the exact errors that the person in the link got, is what I'm saying.
@Helios: I'd love to build the code from source, but I'm saying that I don't know how to do that.
@Helios: I'd love to build the code from source, but I'm saying that I don't know how to do that.
closed account (236Rko23)
well if you don't know how to compile it, better start learning. if you are a programer you'll have to learn anyway.
as far as i've seen it has a folder with VisualC and Code::Blocks proyect files, along with a makefile. Download the source and open de VisualC file and try compiling it, then copy the library and link it in your proyect.
This is the same as the guy was told to do. but he ended up ading the files to the proyect and instead of compiling the library first and then linking, he added the header and compiled the object files and linked them directly
sumarising:
download the source then
A - compile library then use it instead of the other
B - compile the source and link it directly
as far as i've seen it has a folder with VisualC and Code::Blocks proyect files, along with a makefile. Download the source and open de VisualC file and try compiling it, then copy the library and link it in your proyect.
This is the same as the guy was told to do. but he ended up ading the files to the proyect and instead of compiling the library first and then linking, he added the header and compiled the object files and linked them directly
sumarising:
download the source then
A - compile library then use it instead of the other
B - compile the source and link it directly
Well, there's a first time for everyone. Fiddle with it and you're bound to get it eventually.
There's really only two solutions here. One is building from source, and the other is fixing each undefined symbol by tracking down the MinGW .a file that contains it and adding it to the linker input list. If you can't do the former, it's unlikely that you can do the latter.
There's really only two solutions here. One is building from source, and the other is fixing each undefined symbol by tracking down the MinGW .a file that contains it and adding it to the linker input list. If you can't do the former, it's unlikely that you can do the latter.
Alright, I just understood what the issue was.
I was trying to open a VS2009 file, rather than the 2008, and for some reason VSE2010 (that I use) could only convert the 2008 file. In addition, I didn't understand the the project outputted a .lib when you built the solution. Problem solved, thanks.
I was trying to open a VS2009 file, rather than the 2008, and for some reason VSE2010 (that I use) could only convert the 2008 file. In addition, I didn't understand the the project outputted a .lib when you built the solution. Problem solved, thanks.
Topic archived. No new replies allowed.