[osg-users] #include <string> on MSVC results in errors

Voerman, L. l.voerman at rug.nl
Tue Jul 11 04:13:19 PDT 2017


Hi Bruno,
it's very uncommon to have subfolder of osg\include in your include path,
like include\osgText.
The normal configuration has something like E:\dev\OpenSceneGraph\include
in the project include path, and requests the use of the osgText\String
with:
#include <osgText/String>

this way there will be no confusion with the system string haeder files.
Regards, Laurens.

On Tue, Jul 11, 2017 at 12:57 PM, Bruno Oliveira <
bruno.manata.oliveira at gmail.com> wrote:

> Hello,
>
> Windows is not case sentitive, hence, on MSVC 2015,
>
> #include <string>
>
> is the same as
>
> #include <String>
>
> For this reason, I am including <string> to get std::string definitions,
> but MSVC is include <String> from OSG.
>
> Is there a way to fix this? I'm sure this has happened to more people.
>
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20170711/1a0a0a27/attachment.htm>


More information about the osg-users mailing list