That's the whole point, I do not want Developer1 to debug my code (that is compiled with /MD and no /Zi) but I want him to debug his code :) and he will usually compile with /MDd, so if a method of the library returned something like std::string it would mess all up due to heap corruption, so i have to forewarn him that he should compile his debug code with /MD and not with /MDd (that is a constraint i would like not to impose)
So maybe my question could be summed as: intel compiled binary relies on MSVCR90.dll?
Does that make any sense?
Well, as you mentioned before, using /MDd might give access to boundary checking codes and such that Developer1 might want to use to debug his own code. As i said, i would love not to impose any unavoidable costraint.
For example I did check the IPP libraries with dependency walker and they seem not to depend at all on any msvcrt[80|90|100].dll but just on msvcrt.dll (system wide windows c runtime?) how such a task is achieved? compiling with icc would do that? would not this solve the issue?
thanks for your support :)