From: Patrik J. <je...@ka...> - 2006-06-19 12:52:24
|
I do have the correct .Net runtime as far as I know. But I do believe it has to do with the vc++ created dll's. Why they interfer with the mingw created dll's(or app) is a mystery to me... Is it possible that the win32 app created with mingw uses the manifest file in some way or another? thanks Bill Durksen wrote: >Quoting Patrik Jeller je...@ka...: > > > >>There are several ways to know which dll's are loaded. For example the >>debugger shows me what dll's are loaded. But the reason why I noticed >>is, because one of the "not required" dll's produces a runtime error >>because of a missing manifest file (its an vc++ generated dll). >> >> > > > >>... >> >> > >It sounds like you got involved with a .NET assembly. I.e. a set of DLLs >that has one main DLL with a manifest table in it (a type of metadata >directory showing, again, dependencies and more). >Solutions? > a) Get the correct version of .NET runtime: 1.1 or 2.0 > b) Get rid of the .NET DLLs > >Thanks, >Bill > > > >_______________________________________________ >MinGW-users mailing list >Min...@li... > >You may change your MinGW Account Options or unsubscribe at: >https://lists.sourceforge.net/lists/listinfo/mingw-users > > |