/usr/bin/ld: Undefined symbols:
irr::video::ITriangleRenderer2::setTexture(unsigned int, irr::video::CSoftwareTexture2*)
irr::video::ITriangleRenderer2::setRenderTarget(irr::video::IImage*, irr::core::rect<int> const&)
irr::video::ITriangleRenderer2::ITriangleRenderer2(irr::video::IZBuffer2*)
irr::video::ITriangleRenderer2::~ITriangleRenderer2()
irr::video::ITriangleRenderer2::~ITriangleRenderer2()
irr::video::ITriangleRenderer2::~ITriangleRenderer2()
typeinfo for irr::video::ITriangleRenderer2
virtual thunk to irr::video::ITriangleRenderer2::~ITriangleRenderer2()
virtual thunk to irr::video::ITriangleRenderer2::~ITriangleRenderer2()
This looks like the Xcode project is out of sync with the latest changes! If I do not remember to add "writepng.c" I get some Undefined symbols errors for that as well. What files do I need to add or is something else the matter?
CFileSystem.cpp:183: error: 'PATH_MAX' was not declared in this scope
CFileSystem.cpp:184: error: 'fpath' was not declared in this scope
CFileSystem.cpp:184: error: 'realpath' was not declared in this scope
oops sorry.. haven't got a linux box or a mac to test on
how is realpath bad? should it check for existence of the file before calling, or is there something really ugly about this function? i searched google but couldn't find anything
If you read the man page of the function you'll find the note "Don't ever use this method". Basically because the MAX_PATH is not necessarily long enough and thus buffer overruns may occur. There is no alternative proposed, though.
I apologize for being such a noob on this one, but...I am getting the same undefined symbols errors when building the samples. I have tried to add ITriangleRenderer2.cpp to the project but must not know what I am doing. I right clicked on the heading MacOSX-Irrlicht-Engine then selected add-existing files and added ITriangleRenderer2.cpp and on building again, received the same error...what did I do wrong?
never mind, I got it figured out...i was getting a new set of linking errors and didn't read them closely enough to realize that they were seperate from the ITraingleRenderer2 issues