[warnerchang]

Hi! Foamers.

when I was compiling a new solver, I was confused about how to include proper files/libraries in the Make/options?

some codes as follow:

EXE_INC = \
    -I$(LIB_SRC)/finiteVolume/lnInclude \
    -I$(LIB_SRC)/meshTools/lnInclude

EXE_LIBS = \
    -lfiniteVolume \
    -lfvOptions \
    -lmeshTools

Does somebody has any ideas?

And One more question! Are the libraries which are included in Make/options in /home/***/OpenFOAM/OpenFOAM-8/platforms/linux64GccDPInt32Opt/lib

[olesen]

The libraries listed as EXE_LIBS are all "proper" libraries, it just happens that the standard OpenFOAM library location is added automatically. That is to say, there is an implicit -L$(FOAM_LIBBIN) there. If you need to add libraries from other locations, eg -L$(FOAM_USER_LIBBIN) -lyourlib, or -L/cluster/path/lib64 -lsomeOther, you need to specify that.

[warnerchang]

Hi! olesen

Thank you for your help! I am confused about the prefix -L, in my codes, it is started by -l, is there any difference between -L and -l?

And what is the difference between EXE_INC and EXE_LIBS? I mean that they both contian "finiteVolume" and "meshTools". What EXE_LIBS contains is source files? and what EXE_INC contains is just dynamical links?

Appreciate for your reply!

[olesen]

Originally Posted by warnerchang

Hi! olesen

Thank you for your help! I am confused about the prefix -L, in my codes, it is started by -l, is there any difference between -L and -l?
dynamical links?

"man gcc" and you will see what they mean

[Tobermory]

You need to read up a little on compilation, as Mark suggests. In particular - learn about the role of include files (-I) during compilation, and the role of a linker in building an executable or library. Once you understand that, all will be clear!

[warnerchang]

Thank you for reply!

Best regards!