0.8 repo: String.h on Windows
Posted: Sun Jan 01, 2012 02:26
Hey all,
I pulled a CEGUI 0.8 off the repo not too long ago, and managed to compile it with managable levels of trouble (I needed the OgreRenderer). Now, I seem to have a problem. CEGUI's headers include String.h (note the capital letter, which Windows doesn't give a *bleep* about), which includes string.h (note the lack of capital letter, which-... yeah), like so many other headers. So, whenever #include "string.h" was used, one of them would have to be chosen. I got the wrong side of the stick, and every single thing in my whole STL header collection b0rked. Hard. So yeah. It'd be nice to your Windows-using fans to rename it to something other than (case-insensitively) string.h.
Needless to say, having an STL header replaced with a CEGUI one somewhere, and having all other STL headers that require it suddenly go "waitwhut", caused me quite a headache. I'm hoping the same won't happen to anybody else.
That said, I do appreciate the work you folks do. A lot.
I pulled a CEGUI 0.8 off the repo not too long ago, and managed to compile it with managable levels of trouble (I needed the OgreRenderer). Now, I seem to have a problem. CEGUI's headers include String.h (note the capital letter, which Windows doesn't give a *bleep* about), which includes string.h (note the lack of capital letter, which-... yeah), like so many other headers. So, whenever #include "string.h" was used, one of them would have to be chosen. I got the wrong side of the stick, and every single thing in my whole STL header collection b0rked. Hard. So yeah. It'd be nice to your Windows-using fans to rename it to something other than (case-insensitively) string.h.
Needless to say, having an STL header replaced with a CEGUI one somewhere, and having all other STL headers that require it suddenly go "waitwhut", caused me quite a headache. I'm hoping the same won't happen to anybody else.
That said, I do appreciate the work you folks do. A lot.