-
October 18th, 2009, 08:36 AM
#1
Using MFC in a static library, and com port errors
Hi
I have a project where I'm communication with an external device via an RS232 interface.
When I have the project set up to build with debug output and I run it by pressing F5, I have no problems. If a take a copy of the executable to another PC without Visual studio installed it won't run, and I get errors about DLLs missing. After a bit of searching I found a suggestion to statically include MFC in the build. When I set the option to do this I cannot build the project with the debug option set because I get errors about multiple definitions of functions. If I choose the release option the project builds but then says it cannot communicate via the RS232 port.
I know this my be a really dumb question for some, but how do I determine what DLLs my application will need, and how do I ensure that the app can find them when it is being run?
Thank in advance
Andrew
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|