Libraries are often created using a library manager such as xiar for Linux*/macOS* or xilib for Windows*. Given a list of objects, the library manager will insert the objects into a named library to be used in subsequent link steps.
The following command creates a library named user.a containing the a.o and b.o objects:
xiar cru user.a a.o b.o
If the objects have been created using [Q]ipo -c then the archive will not only contain a valid object, but the archive will also contain intermediate representation (IR) for that object file. For example, the following example will produce a.o and b.o that may be archived to produce a library containing both object code and IR for each source file. For example:
ifort -ipo -c a.f90 b.f90
The commands generate mock object files, which when placed in archive will also be accompanied by a true object file.
Using xiar is the same as specifying xild -lib.
When using xilibtool, specify -static to generate static libraries, or specify dynamic to create dynamic libraries. For example, the following command will create a static library named mylib.a that includes the a.o, b.o, and c.o objects:
xilibtool -static -o mylib.a a.o b.o c.o
Alternately, the following example command will create a dynamic library named mylib.dylib that includes the a.o, b.o, and c.o objects.
xilibtool -dynamic -o mylib.dylib a.o b.o c.o
Specifying xilibtool is the same as specifying xild -libtool.
Create libraries using xilib or xilink -lib to create libraries of IPO mock object files and link them on the command line.
For example, assume that you create three mock object files by using a command similar to the following:
ifort /c /Qipo a.obj b.obj c.obj
Further assume a.obj contains the main subprogram. You can enter commands similar to the following to create a library:
xilib -out:main.lib b.obj c.obj // or xilink -lib -out:main.lib b.obj c.obj
You can link the library and the main program object file by entering a command similar to the following:
xilink -out:result.exe a.obj main.lib