[mirko]

Hello,

I am going through Hrvoje's instructions to install OF on my 64-bit RHEL5, and I am having trouble with dx (missing lesstif library, missing link to /usr/include/linux/sys.h). I fixed those two.

But now I am hitting on a conflict in a libtiff declaration which exposes my lack of C programming knowledge. I get the following error:

/usr/include/X11/VendorP.h:87: error: previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage
/usr/local/include/Xm/VendorSP.h:58: error: conflicts with new declaration with 'C' linkage

I found a related message on the Debian board:
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg210855.html

but my version of the file mentioned in the patch already includes it. I am puzzled by this.

So, my question is two-fold:

- is dx essential for OF?
- Any ideas how to try and compile dx?

Thanks,

Mirko

[jaswi]

Hi Mirko

The dxFoam is not essentail to for the core part of OpenFOAM. Its just an utility for the post processing. If you intend to use paraFoam/paraview then feel free to remove the dxFaom folder from the
utilities/postProcessing/graphics/ folder as when not compiled properly it spits out som many errors that you do not want to look at the screen anymore :-)

Also if you are new to openFoam or openDx then i suggest you better stcik to paraview/paraFoam as it has a very small learning curve.

doing post processing with openDx/dxFoam requires some homework

Hope that helps

Jaswi

[mirko]

Thanks, Jaswi,

but as I said, I tried to follow the compilation path that Hrvoje included in dev branch on svn. And that one requires dx :-(.

As for, why did I try Hrvoje's path? Well, the other two had me stymied too :-(

I am guessing that the compiler is being stricter than in the past. But my knowledge of configuring and compiling C is limited to reading the documentation and information I find on the web.

Thanks,

Mirko

[jaswi]

Hi Mirko

I am myself using the Hrv's developer version and I use it without openDx/dxFoam

I again emphasize on the fact that openDx/dxFoam is an option for post processing. I do not know how well do you understand the OpenFOAM code structure so I can just say the following:

OpenFOAM consists of:

OpenFOAM/OpenFOAM-1.4.1/src <--Core OpenFOAM code compiled into libraries.

OpenFOAM/OpenFOAM-1.4.1/bin <--various OpenFOAM scripts that come with the code


OpenFOAM/OpenFOAM-1.4.1/lib <--in there lives the result of your core code compilation. All the code in /src is compiled into shared object libraries and this folder /lib is where all that is saved

OpenFOAM/OpenFOAM-1.4.1/application <--this is the part which we mostly use. inside the folder application you will find the following folders

-bin <-- contains all the executables corresponding to the code in solvers and utilities.

- test <-- contains small programs to test the basic classes

-solvers <-- that is where all the solvers you use live in their naked form

-utilities <-- this folder contains the code for all the pre and post processing utilities. look in their u will find folders like :

mesh
postprocessing
preprocessing
parallelprocessing
surface
thermophysical

etc etc...


Now when you are compiling the code try to compile one thing at a time to have a complete control of the situation. How can you do that must be the question now :-). very simple ...

Look into the Allwmake script in the main folder.
It contains
-----------------------
#!/bin/sh
set -x

(cd wmake ; ./makeWmake)

(cd src ; ./Allwmake)

(cd applications ; ./Allwmake)

if [ $# = 1 -a "$1" = "doc" ]
then
(cd doc ; ./Allwmake)
fi
-------------------------

Just comment this line like this and you will not be compiling the code in application folder

#(cd applications ; ./Allwmake) line

Similar script is there in the /application folder which first compiles the solvers and then utilities. You can do the same at that level as well.

Try to peg the source of error and understand that it will not cause trouble to you work.

Sorry if I was explaining too simple stuff

Hope that helps
JAswi

[mirko]

JAswi,

thanks. That is exactly what I needed. I am not familiar with the source tree, and what needs to be compiled and not. I will give your suggestion a try.

Thanks for your time in helping me resolve this.

Mirko