Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Dawid90dd

Pages: [1]
1
I've installed using mingw64 automated installer mingw with gcc 6.1.0. It works now perfectly.

Thank you.

2
I've unpacked fresh source code archive. I've cleared PATH so it doesn't use MSYS Make. I've used MinGW Automated installer (MinGW Installation Manager) which downloaded for me GCC of 6.3.0. I'm using Windows 7 64 bit on VirtualBox. (my friend has windows 7 64 bit but not on virtualbox and has the same problem) mingw32-g++ is 6.3.0

3
I've changed PATH so it doesn't use MSYS make and uses mingw32-make and MinGW. I've encountered the same error.

I've used

cmake -G"MinGW Makefiles"

mingw32-make -j2

Compiler is still 6.3.0

I do want to compile it on 6.3.0 because all of my libraries are compiled on MinGW with gcc 6.3.0. If that is a problem then i might try to downgrade it to 6.1.0 and use already compiled version of SFML 2.4.2 by you.

My friend tried to compile it on 6.3.0 and is having the same problem.

4
Hello. I've encountered a very annoying error after try of compilation using MinGW with G++ version 6.3.0



I'm building using cmake command:
cmake -G"Unix Makefiles"

And after that:
make -j2

Can you help me? I'm trying to write my own library for game development which uses newest SFML 2.4.2, and i'm encountering this error.

I've also found this topic:
https://stackoverflow.com/questions/46396148/compiling-sfml-with-mingw-has-ptitlebarinfo-not-declared

But it doesn't help me much...

Edit Postscriptum:
I'm also compiling the same library but on linux (ubuntu) but it doesn't throw me any errors. (as i understand this is windows related problem and more peculiarly winapi?)

Also, i know that it says SFML 2.3.2 but i've tried SFML 2.4.1 and SFML 2.4.2, it throws me the same error.

I've found that this issue is related to Window module because it throws errors from window module files

Pages: [1]
anything