We've recently upgraded to Visual Studio 2008 from 2005, and I think that the error started after that.
In our solution, we have several projects, many of these utility projects, or projects with the main functionality used by other projects are the production of those "project dependency ..." option Using Liberal files related to the construction of final binary projects.
One of the other projects- We call it ResultLib --- generates a DLL, and it requires a single function from the core project. This function uses the static function only from its own source file, but its fully project uses very low level functions and imports a DLL --- it's called Driver.dll.
Our problem is that when ExtLib produces, then the linker complains about many different intervals, for example, all operations are exported from the driver dll, because of the reason for libilling Lib file is not specified. If we try to fix it by adding all the link files used by all projects that use all core projects, our resultant ResultLib DLL eventually imports Driver.dll and defines all the tasks defined in it Also exports.
How do we just tell Visual Studio to try to solve the symbols used?
Your Libge Object Phillieser is probably not sufficient grainy if you use a function in a library Another function is included from the same object file, and the functions they call according to the definition will need to be resolved. Take an example:
I have three functions in my library, F1, F2 and F3. I function F1 and F2 are in the same souce file (and Thurman ends in the same object file ). The function F3 is in a separate file.
If I call my application then the F3 will only contain the code for the F3 if my app calls F1 or F2, then the linker will always contain the code for the sour work.
This is the reason that some library projects end up with several small source files.
Comments
Post a Comment