madshi.net

If I want to use source code for compilation and installation, there is no problem under Win32 platform, but under win64 platform, if I refer to the "madTools. pas" unit and do not use the "madTools. dcu" given by the installation, the sample project will be wrong!

I Use 10.3 Rio

I use madExcept 5.0.
I compiled a 64-bit demo, which is 'ExcCatch.exe' provided in the installation program. I compiled it into Win64 program in Delphi 10.3. When I installed madExcept 5.0, some units were installed directly in'C:\Program Files (x86)\ madCollection\ such as'C:\Program Files (x86)\madCollection\madBasic\BDS20\WIN64' , if I delete the files in the directory and copy all the source code from the source folder, the Except Box Form will not be opened at the end of the process. Tests show that as long as the file'madTools.dcu'is not replaced, everything will be normal.If I used 'madTools. pas', it would be abnormal in 64-bit programs.Forgive me for my poor English, I hope you can understand!

So just to make sure I understand you correctly: You're saying that after you've deleted the precompiled DCUs and copied the source files, you were able to successfully compile ExcCatch.exe (without Delphi complaining about anything), but madExcept didn't work properly in the compiled EXE file? And you're saying if you use the precompiled madTools.DCU, everything's working as expected, but if you recompile madTools.pas yourself, madExcept stops working. Is that all correct?

Where exactly did you copy the source code to? Did you copy it to both e.g. madBasic\BDS20\WIN32 *and* madBasic\BDS20\WIN64, so you have the same pas file in 3 folders now (WIN32 + WIN64 + Sources)? And did you copy the madBasic related sources (e.g. madTools.pas) into the madBasic\BDS\WIN64 folder, and the madExcept related source code (e.g. madExcept.pas) into the madExcept\BDS\WIN64 folder?

To be honest, I'm not completely sure what's going on there. Can you compare the EXE file size, when madExcept works or doesn't work? Is it different? Also, can you please try this:

1) Create an empty file "madExceptWizard.txt" on your desktop.
2) Compile your EXE in such a way that madExcept works.
3) Rename "madExceptWizard.txt" to "success.txt".
4) Create an empty file "madExceptWizard.txt" on your desktop.
5) Compile your EXE in such a way that madExcept does not work.
6) Rename "madExceptWizard.txt" to "fail.txt".
7) Zip the 2 text files and upload them somewhere, so I can look at them and compare them.

here is success.txt and fail.txt

The logs both look "good" to me.

Can you confirm that what I wrote in my previous comment is correct: Did I understand your description of the situation correctly?

And does the file size of the working and failing EXE files differ, or is it roughly the same file size?

Your understanding is correct, you can also test, you can delete all the files in the "MadCollection\madBasic\BDS20\win64\" directory, the "madCollection\madBasic\Sources\" under the file copy to " MadCollection\madBasic\BDS20\win64\ ", and then compile the 64-bit 'ExcCatch.dpr', so compiled out of the program, the end will not pop up the report window!

Did you delete the madExcept DCUs, as well, and copy in the madExcept PAS files?

Whether it is a reference to madexcept Dcus or madexcept Pas, as long as not replace the "BDS20\WIN64\MADTOOLS.DCU" will not go wrong, replaced will be a problem!

I have sent my build exe to your email!

i can not sent email,was judged to be spam

I recorded my video and send to your email, please look at it! thanks very much! Video in the email attachment, please use 7z decompression!