[EmadTandis]

Hello
I am new to openFoam programming and want to make some change in some class like gaussLapacianScheme.C located in $WM_PROJECT/src/finiteVolume/finiteVolume/lapalcianScheme/
to the extent that I understood form "Make" directory, the option file in almost all application usually access to this calss using -lfiniteVolme in "option" file. for example the "option" file of one solver is something like below:
EXE_INC = \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(LIB_SRC)/meshTools/lnInclude

EXE_LIBS = \
-lfiniteVolume \
-lmeshTools

My question are:
1- Do the " -I$(LIB_SRC)/finiteVolume/lnInclude " and "-lfiniteVolume " say same thing? also "-I$(LIB_SRC)/meshTools/lnInclude" and "-lmeshTools"?
2- I removed "-lfiniteVolume " and instead of using that dynamic library, copied all files in in $WM_PROJECT/src/finiteVolume to "lnInclude" located in application folder. but I received Error. Why I have to use dynamic library?

I think I have got quite confused with the dependencies and be glad to receive some notes.
Thanks in advance

[chegdan]

To answer your questions:

1. no and no.
2. you shouldn't need to copy files around, you need to just include files and libs to provide enough for the code to compile.

In the options file, there are two sections. The *_INC section will tell the compiler where to look for *.H and *.C files that the code you are compiling needs. The *_LIBS section is a list of all the libraries (e.g. libfiniteVolume.so) within OpenFOAM that are needed. Wmake then puts it all together and helps your compiler ... compile things.

[EmadTandis]

Thanks chegdan for reply
1- If I want to compile finite volume classes and my newApp.C at the same time, and not using -lfiniteVolume, Do you think it is doable? ( I tried but received error)
2- I did the method that you've mentioned (using option file), but it was of no use. So I copied all finite volume classes to my slover's directory to make sure that they are available for newApp.C . As I said the compiler show error while compiling classes file.
Then tried to compile finite volume classes separately (using >>wmake libso command, like what openFoam did), it works.
I just want to know why I can not compile them with the newApp.C at the same time?

[floquation]

Originally Posted by EmadTandis

So I copied all finite volume classes to my slover's directory to make sure that they are available for newApp.C .

As chegdan said, you shouldn't have to do that.

Originally Posted by EmadTandis

1- If I want to compile finite volume classes and my newApp.C at the same time, and not using -lfiniteVolume, Do you think it is doable? ( I tried but received error)

By definition, yes it is possible... But it might be a hassle, as I don't think it will be trivial to use "wmake".
Why would you want to do that in the first place? Your executable will become huge, and your solver will suddenly have openfoam hard-coded, which means that you need to do a lot of changes to your solver if the finite volume library is updated, as opposed to requiring zero changes.

Originally Posted by EmadTandis

As I said the compiler show error while compiling classes file.

No one is going to give you a sensible answer if you tell us nothing. For all we know, the compiler might complain about something unrelated to the linking process.
Read this first.

[EmadTandis]

Thanks floquation
I think i got the point..