Deploying release configuration of application still looking for debug versions of QT dll's
-
Good Afternoon,
I'm in the process of trying to deploy an application that a 3rd party developed using the QT framework for the front end and I'm running into a problem which is I'm getting the following error message:
Activation context generation failed for "E:\PJMAVC\QtCore4d.dll". Dependant assembly Microsoft.VC90.CRT,processorArchitecture="x86"... could not be found.
I built the solution in release mode and included the non-release versions of the QT dll's but if I don't include the QtCore4d.dll in the deployment then I can't even launch the application because it's missing however when I do include it I get the above error message.
This is my first exposure to this framework so any and all assistance is greatly appreciated.
-Bill Youngman
-
Hi and welcome to devnet,
Are you linking to any 3rd party pre-compiled library that might be in debug mode ?
-
No I have all of the source code for the 3rd party solution and have it set to 'Release' for compilation
-
I'd check whether it's referenced anywhere explicitly in the project.
Are you using the Qt VS-Add-In plugin ?
-
I was just going through one of the projects in the solution and I just saw where it is being set as an Additional Dependency along with all of the other xxxd dll's - I'm assuming that these are debug dll's. Going to try removing them and adding the regular dll's to the project and recompile
-
Pretty strange, was it done by hand ?
-
Not sure how it was done - this solution was written by some Electrical Engineering Undergrads who judging by how it was written don't have much software development experience so I'm having to go through the entire thing and try to figure out exactly what they were doing - just removed the dev version of the dll's and included the release versions and now i'm getting a program launch error so back to the drawing board.
Wanted to say though thank you all for the quick responses to my post.
-b
-
You can try to recreate the project using qmake, it might be quicker in the end.
You're welcome :)
-
ok so I got the Release Configuration configured so that it's not pointing to and of the dev dlls but it's still trying to load qcore4d.dll on the target machine - grrrr...
Going to try the suggestion from the last post and recreate the project using qmake
-
Did you check your executable, dlls with e.g. Dependency Walker ?
-
No I haven't - good suggestion
thanks
