-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obj/fe_blend.o fails to compile #446
Comments
Have you tried compiling with full clean? |
do you mean did i run |
Could you try my fork with the recent fixes and tell if the issue is also there ? Also, are you compiling for linux or cross-compiling? |
just run:
same result (compiling for linux) |
What SFML version do you have there? |
|
From what I see you have quite old sfml libs 2.1 Update to 2.4.0 or the latest 2.5.1 to get it compiling. SFML BlendMode was added from what I remember in 2.3.0 |
Attractmode is meant to work on any sfml 2.x version. I didn’t realize blendmode was only added with sfml 2.3 when this was merged. This is a bug in Attractmode that will get fixed when I am able to work on it again (in about 3 weeks)... thanks for reporting this
… On Jun 1, 2018, at 2:22 PM, Radek Dutkiewicz ***@***.***> wrote:
From what I see you have quite old sfml libs 2.1 Update to 2.4.0 or the latest 2.5.1 to get it compiling. SFML BlendMode was added from what I remember in 2.3.0
Is there any particular reason you got the dev package? I think those are the libraries for debugging sfml.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Actually to be precise it’s about constructing custom blend modes which I used for non standard blending. The standard blending modes were present in earlier sfml versions |
What do you do in that kind of situations? |
Andrew, would you please explain to me what is the reason of keeping the compatibility with the old SFML libraries? |
Well the main reason is that the compile instructions in compile.md state that any 2.x version of SFML is what is needed to compile.
Beyond that, I want it to be as backwards compatible as possible (within reason) because there are many reasons why people may not be able to use the most recent sfml (Debian and some other linux distros don’t get released that often, etc.).
… On Jun 3, 2018, at 10:11 AM, Radek Dutkiewicz ***@***.***> wrote:
Andrew, would you please explain to me what is the reason of keeping the compatibility with the old SFML libraries?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi there, I'm unable to reproduce this here but some changes have been made that might fix this. Could you try compiling again with the latest code from master and let me know if it fixes this? thanks |
hi, I tried to compile again on the same system (debian jessie) and after issuing it fails in the very same way (except for slightly different line numbers):
|
Calling BlendMode constructor will fail on older SFML versions. Some additional checks for the SFML versions will be required or just simple try catch block. |
ok i think I've got it now, could you try updating and compiling again?? |
it works! thank you :-) |
hello there,
i am having issues compiling attractmode from latest git (relevant compiler output below)
i'm running debian jessie, and did not have any issues compiling from source until recently.
ciao!
The text was updated successfully, but these errors were encountered: