Messages

1

General / Anyone having problems with the new Visual Studio update?

« on: August 07, 2016, 05:19:39 pm »

I have been tying to build a debug version of the static library's using Visual studio 2015 Update 3 x64.  The reason being is I wanted the debug symbols.  Easy enough.  I downloaded a fresh copy of the source.  Loaded up cmake and unchecked "BUILD_SHARED_LIBS" and checked "SFML_BUILD_EXAMPLES"

The problem is that I am getting linker errors with the examples.  I tried win32 and had the same linker errors.  I have a suspsion its the Update 3 I downloaded as I didn't seem to have this problem a few months back?

Anyone else having this issue?  If not it might just be my setup.

2

Feature requests / Re: Remove the jpeglib.lib or replace with a header only?

« on: August 07, 2016, 02:58:28 pm »

Your quite right of course.  There is nothing wrong with using jpeglib.  I was just was doing some google searches at the time and came across TinyJPEG and just got me thinking.  I was having problems using the already precompiled librarys on a x64 static build I was trying out and was trying to narrow down the dependency that had issues.  jpeglib being one of them:P

3

Feature requests / Remove the jpeglib.lib or replace with a header only?

« on: August 04, 2016, 03:41:33 pm »

I was having some issues compiling sfml for x64 bit as a static lib in Visual studio.  I can handle figuring out how to do the library dependency but as I was looking though the code I noticed that the jpeglib library is used in only ONE spot.  Specifically writeJpg in ImageLoader.cpp.  The stbi package is used for everything else.

Don't get me wrong, I do want to be able to save in jpeg.  People should be given a choice.  I am just wondering why a header only library can be used.  (For example, TinyJPEG:https://github.com/serge-rgb/TinyJPEG that I used to replace it with)

Just a thought.  Was struggling with getting jpeglib to comple till I found somones sln online:P