Home > Software engineering >  MFC after you've written, in other computer
MFC after you've written, in other computer

Time:10-06

I'll copy realse folder to another computer, open exe will be xx. Exe encounter problems need to be closed, we apologize for the inconvenience caused by

Should be my program calling a DLL,,
I am a static call, and there is
Joined..lib file, including the. H file, in the lib and DLL are copied to realse folder inside, then direct call DLL function within the

In your computer, it is normal,
Copies to other computers, programs as long as the operation to function in the DLL can appear the above error,

Great god answer,,,,,,,, tried a day, have no, thank you

CodePudding user response:

Inside the connector input your DLL project put in

CodePudding user response:

Estimate it is other systems and you have a DLL compatibility problem, try a static link to the MFC

CodePudding user response:

reference 1st floor SWWLLX response:
inside the connector input your DLL project add


Kindness, useless, the other is still an error

CodePudding user response:

refer to the second floor pcradio response:
estimates it is other systems and you have a DLL compatibility problem, try a static link to the MFC


Static link, is the configuration properties that, inside, I into a static linked, and exe then become larger, but still have problems in other machines,

CodePudding user response:

What is your development platform system, Windows 7?
What system is another machine?

CodePudding user response:

did you tried the dynamic linking

CodePudding user response:

reference 5 floor pcradio reply:
what is your development platform system, Windows 7?
What system is another machine?


I am xp, and another computer, Windows 7

CodePudding user response:

refer to 6th floor SWWLLX response:
did you tried the dynamic linking


You mean is to use LoadLibrary and GetProcAddress call to load the DLL? That to also have no

CodePudding user response:

refer to the eighth floor qq_24648053 response:
Quote: refer to the fifth floor pcradio reply:

What is your development platform system, Windows 7?
What system is another machine?


I am xp, and another computer, Windows 7

What is the development environment? VC6?

CodePudding user response:

Use depends. Exe view exe dependent DLLS

CodePudding user response:

If the problem is simply an exe file, then compiled into static link, if you have to load other DLL files, confirm whether DLLS need to register first, again, to load the DLL file whether there are other dependent libraries,

CodePudding user response:

No good implementation in the Windows 7 installation vs debugging

CodePudding user response:

Call the DLL will have problems in machine? Only path problem, I can imagine what is loaded with the absolute path of the building Lord, as for the system compatibility, generally don't call the third party an excuse, does not have this kind of problem

CodePudding user response:

To make the installation package or on the computer to run in VC6 (short version)

CodePudding user response:

On the 14th floor qq_29700255
reference response:
call DLL will have problems in machine? Only path problem, I can imagine what is loaded with the absolute path of the building Lord, as for the system compatibility, generally don't call the third party, won't have this kind of question

In addition, the original poster can drag your release files to the desktop (that is, change the file path) try, if is normal path problem, and yes. It is little impact in the computer the question, unless you need to change what operating system configuration environment such as configure odbc
  • Related