unit 'madExcept' not found in binary file
Thanks a lot!madshi wrote:Your exe tries to use madExcept_.bpl as a runtime package. That's currently not supported! Please remove madExcept_.bpl from the list of runtime packages (project options). madExcept.pas must be linked into your executable.
Really, exe was succesfully patched.
I fail to attend this preivious message:
It means, if I have exe and runtime bpl (used in this exe), I can't use madX units in my bpl?madshi wrote: Currently madExcept doesn't support linking madExcept.pas into a package.
Or this feature will appear in
?[/b]madExcept 3.0 which will support that (due out in a few weeks)
You can use all mad* units in your bpl, just not madExcept.Tolyan wrote:It means, if I have exe and runtime bpl (used in this exe), I can't use madX units in my bpl?
Yep, with madExcept 3.0 you'll be able to put madExcept.pas into your bpl, as well.Tolyan wrote:Or this feature will appear in?madExcept 3.0 which will support that (due out in a few weeks)
Khe-khe...madshi wrote:I think you can add madStackTrace to your bpl, I've not tested that yet, though. Basically the only thing which you may not add to the bpl is "madExcept.pas".
Experiment with exe and 2 bpls:
Goal: raise exception in form from 1st bpl and see madExcept message dialog
In)
1) use madExcept in my exe (check madExcept setting "handle exception")
1st experiment:
In) 2) not use madStackTrace in my 2nd bpl (functionality was commented)
Out) Cool - madExcept message dialog was appeared
2nd experiment:
In) 2) use madStackTrace in my 2nd bpl (with required madExcept_.bpl)
Out) Suxx - madExcept message dialog was not appeared
3rd experiment:
In) 2) use madStackTrace in my 2nd bpl (implicitly imported units
madCrypt.dcu, madDisAsm.dcu, madMapFile.dcu, madStackTrace.dcu,
madStrings.dcu, madTools.dcu, madTypes.dcu, madZip.dcu)
Out) Suxx - madExcept message dialog was not appeared
I think - 3rd madExcept will appear - 3rd madExcept will help me!
Or not?!