[osg-users] 'fatal error C1128: number of sections exceeded object file format limit' under MSVC2015

186 views
Skip to first unread message

Jason Beverage

unread,
Apr 18, 2018, 3:59:34 PM4/18/18
to osg users
Hi Robert,

I'm compiling the master in debug with MSVC 2015 and running into this issue again:  http://forum.openscenegraph.org/viewtopic.php?t=16012&start=0&postdays=0&postorder=asc&highlight=

This time it's with Geode.obj

I've added /bigobj just to get it building here locally.  Not sure if there is anything else we can take out of the headers to slim it down or not.

This is my first time seeing this issue so I'm not 100% sure if it's a good idea to just enable /bigobj all the time or not.

Jason

Robert Osfield

unread,
Apr 19, 2018, 3:14:38 PM4/19/18
to OpenSceneGraph Users
Hi Jason,
I don't have any VisualStudio expertise so have to defer to Windows
devs as how best to guide the build with VisualStudio. So if you feel
adding /bigobj is required then submit a PR to add this.

What are the cons about enabling /bigobj?

Robert.
_______________________________________________
osg-users mailing list
osg-...@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

sam

unread,
Apr 19, 2018, 4:44:48 PM4/19/18
to OpenSceneGraph Users
Hi Robert,

Enabling -bigobj just changes the address space for obj files. The default is 2^16 and /bigobj will enable 2^32. The only con that I'm aware of is linker's that shipped prior to Visual C++ 2005 cannot read .obj files that were produced with /bigobj.


Looks like most of the projects now force it on in CMAKE.

Thanks, Sam



On Thu, Apr 19, 2018 at 1:14 PM, Robert Osfield <robert....@gmail.com> wrote:
Hi Jason,

On 18 April 2018 at 20:59, Jason Beverage <jasonb...@gmail.com> wrote:
> I'm compiling the master in debug with MSVC 2015 and running into this issue
> again:
> http://forum.openscenegraph.org/viewtopic.php?t=16012&start=0&postdays=0&postorder=asc&highlight=
>
> This time it's with Geode.obj
>
> I've added /bigobj just to get it building here locally.  Not sure if there
> is anything else we can take out of the headers to slim it down or not.
>
> This is my first time seeing this issue so I'm not 100% sure if it's a good
> idea to just enable /bigobj all the time or not.

I don't have any VisualStudio expertise so have to defer to Windows
devs as how best to guide the build with VisualStudio.  So if you feel
adding /bigobj is required then submit a PR to add this.

What are the cons about enabling /bigobj?

Robert.
_______________________________________________
osg-users mailing list
Reply all
Reply to author
Forward
0 new messages