I have the same problem as EzraBC.
Strange, because last time I used it I had no such problem.
Are we doing something wrong?
I can't use the .sln file to build the library myself because my MSVC version is too old (2005).
SOIL: new lightweight image loading lib
Author
Hi, all.
As you know, SOIL uses stb_image internally for most if the loading/saving functionality. In recent times Sean updated his stb_image code to be thread-safe. In doing so he apparently made a bunch of changes that are compiler specific. I didn't notice at the time, and I was only distributing a precompiled lib made with MinGW. It used to work on all compilers, but now that stb_image uses compiler specific functions, SOIL now needs to be compiled on each target compiler.
SOIL ships with a number of project files: Code::Blocks, a makefile for GCC (Linux and Mac and MSYS folks), Visual Studio 6, 2003, 2005, 2008 (in the VC6, 7.1, 8, 9 directories, respectively). So everybody should be able to build it on their dev machine, in theory. Is this a problem? Should I just have N compiled library files ready to go in the zip?
Jonathan
As you know, SOIL uses stb_image internally for most if the loading/saving functionality. In recent times Sean updated his stb_image code to be thread-safe. In doing so he apparently made a bunch of changes that are compiler specific. I didn't notice at the time, and I was only distributing a precompiled lib made with MinGW. It used to work on all compilers, but now that stb_image uses compiler specific functions, SOIL now needs to be compiled on each target compiler.
SOIL ships with a number of project files: Code::Blocks, a makefile for GCC (Linux and Mac and MSYS folks), Visual Studio 6, 2003, 2005, 2008 (in the VC6, 7.1, 8, 9 directories, respectively). So everybody should be able to build it on their dev machine, in theory. Is this a problem? Should I just have N compiled library files ready to go in the zip?
Jonathan
Quote:Original post by lonesockCan we get a source-only zip as well? I *never* want any form of binary, so it is wasted space.
Is this a problem? Should I just have N compiled library files ready to go in the zip?
Loving it. Thanks!
Thanks for giving us all the different project files to make the compile process ALOT easier. Since I'm a total noob with compiling libraries and I almost 99.9% of the time won't get the libraries to compile for the stupidest reasons but this one I did since I was supplied with everything. Thanks!
So far the librarys been awesome :)
Thanks for giving us all the different project files to make the compile process ALOT easier. Since I'm a total noob with compiling libraries and I almost 99.9% of the time won't get the libraries to compile for the stupidest reasons but this one I did since I was supplied with everything. Thanks!
So far the librarys been awesome :)
This library is all kinds of badass. It was a pleasant surprise when I didn't even have to change a few of my functions to transition from my loaders to SOIL. Maybe that's not as unlikely as it seemed to me at the time...at any rate: Thank you very much, lonesock. You rock!
hi
i ve got problem with soil for a 2d opengl engine
rendering quality is bad especially when i ve got color gradients on my textures.
dont know why, but I m sure that the problem is related to soil options , because when i use my own LoadBitmap code , i dont get this problem
http://www.vm-games.com/imgs/in_jpg.jpg
http://www.vm-games.com/imgs/in_engine.jpg
i cant explain because i m using the same filtering (linear) with both soil code and load bitmap code
any ideas?
i ve got problem with soil for a 2d opengl engine
rendering quality is bad especially when i ve got color gradients on my textures.
dont know why, but I m sure that the problem is related to soil options , because when i use my own LoadBitmap code , i dont get this problem
http://www.vm-games.com/imgs/in_jpg.jpg
http://www.vm-games.com/imgs/in_engine.jpg
i cant explain because i m using the same filtering (linear) with both soil code and load bitmap code
any ideas?
Author
Quote:Original post by velk
hi
i ve got problem with soil for a 2d opengl engine
rendering quality is bad especially when i ve got color gradients on my textures.
dont know why, but I m sure that the problem is related to soil options , because when i use my own LoadBitmap code , i dont get this problem
http://www.vm-games.com/imgs/in_jpg.jpg
http://www.vm-games.com/imgs/in_engine.jpg
i cant explain because i m using the same filtering (linear) with both soil code and load bitmap code
any ideas?
Any chance you could post the code you're using to load the image via SOIL? Is it possible you have DXT compression enabled? Depending on the resolution of the original image and the options you've supplied to SOIL, SOIL may be upsizing the image to a power of two, which could lead to stair-stepping like that over long gradients.
Hi,
I'm also having these same linker errors when I try to use SOIL:
1>libSOIL.a(stb_image_aug.o) : error LNK2019: unresolved external symbol __alloca referenced in function _stbi_zlib_decode_noheader_buffer
1>libSOIL.a(image_helper.o) : error LNK2019: unresolved external symbol _sqrtf referenced in function _RGBE_to_RGBdivA2
MatthewBurk says it was fixed by "building a new SOIL.lib". I wonder if you could go into a little more detail? (I'm kinda new to visual).
I'm also having these same linker errors when I try to use SOIL:
1>libSOIL.a(stb_image_aug.o) : error LNK2019: unresolved external symbol __alloca referenced in function _stbi_zlib_decode_noheader_buffer
1>libSOIL.a(image_helper.o) : error LNK2019: unresolved external symbol _sqrtf referenced in function _RGBE_to_RGBdivA2
MatthewBurk says it was fixed by "building a new SOIL.lib". I wonder if you could go into a little more detail? (I'm kinda new to visual).
Actually, it fine now. Yeah, its the SOIL.lib file in the project that's provided. Include that and it is fixed.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
