Messages

1

SFML projects / Re: Selba Ward

« on: October 13, 2016, 10:08:47 am »

Feels bad to bother you again with questions, Hapaxia, but can I ask with what compiler and what os in mind did you designed SelbaWard?

Just had multiply issues with ambiguous call to overloaded function with abs call somewhere in Sprite3d, in short it's all like in that SO question:
http://stackoverflow.com/questions/30084577/ambiguous-call-to-abs

Not sure if it's SelbaWard issue, though, it can be some interference from my side, still can't allow myself enough time to do proper testing due to work, sorry. Right now just hacked some more #include <cstdlib> in every .cpp that have had this issue, it's Line, PieChart, Ring, SpinningCard, Spline, Sprite3d and may be somewhere else I forgot, gonna clean up later. But I think you might be interested in knowing about that issue.

I'm still promise: just after I getting my things done on that week I'm gonna do some real testing to help you with your brilliant work on Selba Ward =)

2

SFML projects / Re: Selba Ward

« on: October 12, 2016, 09:28:39 am »

Hi and thank you for your attention to your project, Hapaxia.

Issue already been solved by a hack on my side, just had a quick glance at your fix - you did the same thing with removing inline. So I'm sure it's right assumption you had there. Now it's linking allright. Kinda strange that no one had this problem before though, may be it was specific to MinGW. I'm gonna try my project with another compilers when it's over and post here if I'm to find anything else.

Thank you again for your work on SelbaWard, it's irreplaceable addition to SFML.

3

SFML projects / Re: Selba Ward

« on: October 01, 2016, 11:57:34 am »

Hi. Got a strange issue with a SelbaWard, can anyone help me?
When compiled for release I got some strange linking issue:
./Release/application.cpp.o:application.cpp:(.text+0x30b7): undefined reference to `selbaward::Line::isThick() const'
Compiler is MinGW (i686-posix-dwarf) with -O2 -std=c++11 -Wall -DNDEBUG under Windows.
With some vodoo I found that problem arose when compiling with any of -O keys and it's bothering me. I can't afford myself to compile without optimization, 'cause it's quite big project with massive calculations that should work on rusty toasters, my customer be damned.
So, any bright ideas? Excuse my english, not native.