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

[Bruno Oliveira]

I agree. However, somehow, using CMake, the include/osgDB folder got
appended to the include path.... This did not happen previously

2017-07-11 12:13 GMT+01:00 Voerman, L. <l.voerman at rug.nl>:

> 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
>>
>>
>
> _______________________________________________
> 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/a219465a/attachment.htm>