Manifest problems

[Guy Fawkes]

"JH Trauntvein" <j.trauntvein at comcast.net> wrote in message
news:1157470492.127691.217210 at b28g2000cwb.googlegroups.com...
>
> Guy Fawkes wrote:
> > wxMSW 2.7.0-1
> > Visual C++ 2005 Express Edition
> >
> > I've compiled the wxWidgets library and there is a wx.manifest file in
the
> > include\wx\msw directory.
> >
> > I've compiled a project (which I converted from Visual C++ 6 and which
> > compiled and ran fine under it) and the compilation seems to go well
under
> > Visual C++ 2005 Express Edition (thanks to the wxWiki).
> >
> > I'm now getting linker errors, though:
> >
> > Linking...
> > Creating Manifest...
> > .\wx\msw\wx.manifest: general error c1010070: Failed to load and parse
the
> > manifest. The system could not find the specified path
> >
> > The project executable *IS* created, though I can't seem to start it
since
> > it can't find the MSVCR80.DLL. It's on the hard drive but I can't just
copy
> > it to the directory where the executable resides. It seems MS has made
it
> > more difiicult to get something working, probably has something to do
with
> > .NET.
> >
> > It looks like it's trying to create the manifest for my project and it's
> > tyring to find the wxWidgets manifest and can't find it. The wxWidgets
> > include directory is in the include path, though.
> >
> > Anyone know what I need to do to get this to work properly?
>
>
> You might be facing two issues, one with loading the c++ run time DLL.
> The other is someting that I ran in to a while back.  It turns out that
> the wxWidgets resource file, which you generally need to include in
> your own, also incorporates a manifest resource.  The problem that I
> ran into was that I had already created a manifest resource for my
> application so I got really nasty link and load errors.  The wx.rc file
> uses a precompiler macro, wxUSE_NO_MANIFEST, to control whether that
> manifest is included.  I attempted to define this in my project and
> found that it didn't seem to work so I wound up editing the wx.rc file
> to remove the manifest manually.  I have since found out that, under
> visual studio 2005, the project manager uses its own set of definitions
> for the resource compiler and none of the c/c++ compiler definitions
> filter over.

I turned off the manifest creation in the project options. This solves me
getting an error during the linking stage. However, the executable won't
start because of the missing MSVCR80.DLL. I looked on the disk and it's
there but in a very strange place:
Windows\WinSxS\x86_Mcrosoft_VC8-_CRT_<some characters>

When I copy the DLL to the application directory it still won't start, I get
an initialization error.

In the Wiki it says that compiling the C runtime library into the executable
is a bad thing but I wonder why, as I'm seriously contemplating this to
solve my problem. I do have a hunch that the manifest and dynamic linking
problems are related.




-- 
Posted via a free Usenet account from http://www.teranews.com