\irrlicht-1.8.3\source\Irrlicht\CFileSystem.cpp|515|error: '_MAX_PATH' was not declared in this scope|
\irrlicht-1.8.3\source\Irrlicht\CFileSystem.cpp|521|error: 'tmp' was not declared in this scope|
\irrlicht-1.8.3\source\Irrlicht\CFileSystem.cpp|614|error: '_MAX_PATH' was not declared in this scope|
\irrlicht-1.8.3\source\Irrlicht\CFileSystem.cpp|620|error: 'fpath' was not declared in this scope|
\irrlicht-1.8.3\source\Irrlicht\CFileSystem.cpp|620|error: '_fullpath' was not declared in this scope|
It sounds like you somehow got __STRICT_ANSI_ enabled in compiling.
Someone had that in the past (http://irrlicht.sourceforge.net/forum/v ... =4&t=49091), but I still don't understand why it would be enabled for some people. It's not enabled in the project file as far as I can see.
That's unless MinGW has changed the stdlib header (look for _MAX_PATH in MinGW/include/stdlib.h if there are any other conditions now).
edit: Also please tell us which Build target you did use.
There is an assumprion, why it is. Which c++ standart whould be using in irrlicht building ? I used c++11 (compiler flag: -std=c++11) and got that errors, now I disabled c++11 and building was correct o_O... Build Target - All.
Hm, yeah - that version has no c++11 support yet (Irrlicht 1.8.4 hopefully will have it). Thought I didn't know so far that _MAX_PATH is affected by that - very strange.
OK, found it. For whatever reason g++ on MinGW does define __STRICT_ANSI__ when you compile with -std=c++0x (my version had no -std=c++11 yet, but I suppose it's the same there). You can prevent that by compiling with -std=gnu++0x or by adding -U__STRICT_ANSI__ which will remove the __STRICT_ANSI__.
I'll try to figure out for next release if we can work around that **** somehow.
