ansaurus

Question

Why do I need an *.obj file when statically linking?

Answer 1

+2 A:

Ah... Visual studio is being too clever for you

Go to the projects that include the lib, right click for properties

Goto Configuration Properties | Linker

Near the bottom : Use Library Dependancy Inputs - Set to No

This is a Visual Studio option to grab the .obj files directly rather than the .lib file. I imagine it is to avoid the link step and thus speed up the compile.

In general, you should set the project that creates the lib file as a dependancy of the project that uses it (under common properties in that properties window). You then turn on Link Library Dependancies. This works well in most cases.

Tom Leys 2009-05-21 02:11:19

I have this set to no already.

Veehmot 2009-05-21 02:40:38

Answer 2

+3 A:

Generally, static libs do not generate object files. What you do is create object files and place them in a library, then the linker will search for the object files in those libraries.

I'll explain from a UNIXy command line point of view since that's the simpler to understande (I have no idea what machinations VS does before doing the basic stuff).

A sample command line for creating an executable is:

gcc -c -o prog.o prog.c
gcc -o prog prog.o -L/libdir -lstdc

The first line simply creates an object file from your C file. The second line creates the executable by pulling object files together, generally following a rule set like:

All .o file listed explicitly are linked.
Once that's done, you search the libraries for other objects which satisfy referenced-but-undefined symbols.

For example, say your prog.c contained the line printf("hello\n");. That will have resulted in your prog.o file containing a reference to printf that is not yet satisfied.

The linker will search your specified libraries until it satisfies that reference. In this case it will search all files of the form /libdir/libstdc.ext where:

/libdir is from your -L option (a path to search for libraries in).
/lib is a constant.
stdc is the name of a library to search (from -l).
ext is one or more extensions (.a, .so, .sl, etc).

Once the symbol is found, that object file is linked in to resolve it. This may result in more unsatisfied symbols appearing such as /libdir/libstdc.a(printf.o) having a reference to /libdir/libstdc.a(putch.o).

Your particular problem may be caused by the fact that you're trying to link the object file directly rather than searching the libraries. VS should have project options to specify object files, library search paths and library names (I'm not sure of this for the latest versions but I know earlier versions of MSVC did).

paxdiablo 2009-05-21 02:12:10

Nice post. It does sound like a MSVC config issue though.

Tom Leys 2009-05-21 02:14:29

Thanks for this, very useful information, but this does not resolve my problem. I want to know a way to avoid the *.obj dependency.

Veehmot 2009-05-21 02:41:55

Answer 3

+1 A:

My mistake:

nsglCore instead of nsglCore.lib

Thanks for your time.

Veehmot 2009-05-21 03:48:37

Answer 4

+4 A:

I believe that your linker line is incorrect. The library should have a .lib suffix on it. So nsglCore should be nsglCore-Win32-Release.lib or maybe nsglCore-$(TargetPlatform)-$(ConfigurationName).lib or whatever the correct macro expansion is.

D.Shawley 2009-05-21 03:49:05

20 seconds after I found it out! See my post. But, this is the answer ;)

Veehmot 2009-05-21 03:51:02

ansaurus

tags:

views:

answers:

Why do I need an *.obj file when statically linking?

related questions