   Unresolved external hell
  If anyone can help me on this, you would rock.I have compiled 4 static libraries (as 4 different projects using VS.NET 2003) into a single /lib directory.  All of the required headers are in a neighboring /include directory.I have a 5th project, which is a console application.  This console app is including headers from those static libs and linking to them.  The project compiles fine, but when LINKING I get unresolved external symbols errors for any function that I call from the static libs.I have checked... the libs are included on the command line (put there via project settings).  The paths are correct... the linker is finding the libs. I have tried to build by simply adding the libs to the path and additional depencies list, and and I have also adden the other 4 projects to the solution and marked them as dependencies.Does anyone know why the functions aren't being "exported" from my static libs?   
  That's a tough one - there are a lot of variables that we don't know.  Have you tried linking to other (known) static libs just to make absolutely sure that you have everything set up right?  Also, have the static libraries you created ever been used before?  Perhaps you didn't expose the functions properly. This could be a real devil. Good luck. :)   ;  Well, I just took the source from some 10 year old C libs and added them to a project (actually 4 projects for 4 libs).  I then had to make a few trivial changes to get it to compile.I have yet to get the functions contained in those libs to work... always unresolved.As a test, I added a project called "StaticLibTest" with StaticLibTest.cpp and StaticLibTest.h.  I linked to StaticLibTest.lib and it allowed me to call StaticLibTestFunc() with no problems.Quote:Perhaps you didn't expose the functions properly.How might I have not done that?  I've never had to do anything before... you just declare, implement, compile to .lib.   Is there some way to exclude symbols and functions that maybe I accidentally "used"?   ;  Does any one know of a tool or something that will show me which symbols/functions are provided by a static .lib file?;  Well, It could be a problem with C++ vs C linkage. If the libraries are C, and your project is C++, try including the library header file like this:extern "C"{  #include <myinclude.h>}   ;  Oooh... It could be.  I thought extern "C" was only supposed to be used, though, when declaring/defining functions that would be used by C code, rather than when using C code from C++.I will certainly try it though.  Thanks for the idea.   ;  AP, you need to post your true identity so I can hunt you down and give you a big fat kiss! [grin]It worked... I don't understand why, but it did.  One hitch... the libs to which I was linking were compiled as C++ code (which makes the problem even more perplexing in the first place).  I had to actually recompile as C, then add the extern "C" block for the includes.   