#ifdef __cplusplus
extern "C"
{
#endif
#ifdef __cplusplus
}
#endif
I'm working for 15 years in Visual C++ and all these libraries are included by the wizard, that why I don't know :See: That is exactly why I hate VS. It gives you no in-sight, makes some hocus-pocus and it somehow works as the VS compiler/linker probably is tweaked accordingly. However, once you want to port or switch to another build system you are in hell.
The order of the library is important for linking...
I know a way : Into Project/Targets options, with dependencies button I could make a dependencies to lib files but it is strande to must do it manually.But I continue to think... it strange that the compiler not the the lib have changed automatically...
Can you say what are the implementation problems?Look: C::B handles dependencies just fine. It's really just a matter of the project setup. You can setup project dependencies and order the targets in a project as need and all will work just fine. If you create a virtual target across all projects in a workspace that will compile the modules as needed your compile process will never fail. In addition I usually resolve missing linker symbols step by step which ensures the right order automatically. Remember that you only have to do it once.
There is really no hocus-pocus needed. Just knowledge about your dependencies and a correct project setup.
The question is can we implement it reliably? :lol:I honestly believe no.
And what are the possible problems?Well - try to do it (configurable) for a number of (partially unknown) compilers (think f copies of compilers) and platform depended. So the same compiler on another platform will have different dependencies. Try to work out a concept and you most likely will fail. It works for MS because they have one compiler and one platform. It's easy to do it that way. But if you really come up with a good approach... I am very interested in hearing it!
I have added dependencies with all .a (lib) that the exe used and all work fine now.That's exactly the steps you had to do. :-)
I'm working for 15 years in Visual C++ and all these libraries are included by the wizard, that why I don't know :See: That is exactly why I hate VS. It gives you no in-sight, makes some hocus-pocus and it somehow works as the VS compiler/linker probably is tweaked accordingly. However, once you want to port or switch to another build system you are in hell.
The order of the library is important for linking...