Hi Hartmut,
it will have bindings to two different C
runtimes. Intermediate manifests are forcibly linked into your binaries.
What? I thought the runtime version issues only affected the C++
runtime, not the C runtime? At least with VC++ 2005, pure-C libraries
had no issues with runtime
Hi Robert, Hartmut,
The changes seem sound, I'd like to see if there
are any side effects though, so I'll test the changes in a fresh build
linked to a small application tomorrow. I'll let you know what I find out.
Change #1 (refer to the original e-mail from Hartmut) is ok, it's a
small
Hi JS,
Thanks for the testing.
The fact that Change #1 does change a function to become a inline
implementation does change the ABI, not a problem from 2.9.x but does
rule out being part of OSG-2.8.1 as so far there has been not ABI
breaks despite all the bug fixes.
Feedback from others please
Dear all,
for the sake of completeness some more of my findings (wrapped in a
lengthy rant about Windows development) here.
- the osgDB::fopen is only the tip of the iceberg
- the whole thing is futile if you need to rely on prebuild 3rdparty
binaries as chances are high the patch version
Hi All,
Hartmut submitted some Windows specific build changes to the OSG and
called for feedback, and I follow up with a request for feedback on
these changes. Alas not a single reply
Any chance that Windows experts you review Hartmut's changes. I can't
personally make a decision on this
Hi Robert,
Hartmut submitted some Windows specific build changes to the OSG and
called for feedback, and I follow up with a request for feedback on
these changes. Alas not a single reply
I've been very busy on my side so I haven't followed this thread as much
as I would have liked. The
Hi Hartmut Windows users,
Has anyone tested Hartmut changes? Hartmut changes look like there
would be appropriate for merging into the OSG-2.8, but I won't do this
till we're absolutely sure there is no collateral damage.
Harmut could provide a bit more information about why these changes
are
Dear all,
hunting around for a while with plain VMware images and rebuilding
everything constantly I drilled down to the cause of the problem which I
reported earlier which turns out to be twofold:
1) osgDB::fopen is opening a file (fopen) in the scope of osgDB dll and
various plugins and
8 matches
Mail list logo
