Since writing the ios framework, compiled after the real machine calls wrong, but compiled simulator is called normal, why?

According to online tutorials, self-written program that ios framework and its called, its export interface is c + + function. After compiling debugging, two programs to edit iphone simulator run call normal,

But the two programs have been replaced with real machine iphone5 compile, debug. framework compiled successfully, you can see its configuration file export and simulators, like orange, with lipo-info xxlib see displayed as: armv7 (cputype (12) cpusubtype (11))

Will be added to the calling program, always shows export header file is red, can not find, but actually exist. Because the compiler can not find the so called program always fail!

Ask you, this may be what causes. Why the real machine even from writing framework will not find interface file, but it is a good way to simulator. In the framework, the real machine and emulator configuration is the same as yo! Wing trouble we are extremely grateful!
Reply:
Ask, you are creating a static library file or Framework?
Reply:
Compiler option when compiling debug framework to release it.
Reply:
A framework.

Thank yang8456211, I ask, framework can be exported C + + classes do?
Reply:

reference to the third floor diaya reply:

a framework
.
Thank yang8456211, I ask, framework can be exported C + + classes do?

I have not tried, but the framework is actually just put some common code together, xcode can compile c + +, so the framework should be no problem.
Reply:
Real machine debugging Organizer can see the error message
Generally not up and running are not caused install name.
Reply:
Thank you, I have resolved, with lipo framework to integrate the two, and then tune just fine.