[hjasak]

you are wasting your time: to get this to work, you have to compile dx yourself with --enable-shared option

[alexandrepereira]

Hi Hrvoje

My question can be a noobish one, but here it is...:

I extracted dx...tar.gz

inside dx folder i typed

alex@iskandhar:~/Desktop/dx-4.4.4$ ./configure --prefix=/home/alex/Desktop/dx --enable-shared

the final lines of the configure process are...

checking lex output file root... configure: error: cannot find output from :; giving up

What can i do here?

Thanks in advance

Alex

[alexandrepereira]

Hi again,

Just one more question...

In case i do not get dx to work with OpenFOAM, what post processor would you advise me to use? Ensight or FieldView?

meaning which one is more robust in large/huge datasets (in the Gigs range ) ?

I'd really prefer to use Dx since it is more customizable, or Paraview, but paraview is not stable on large datasets, and i cannot get dx to work...

Alex

[dmoroian]

Hi Alexandre,
As Hrv said, the best way is to compile OpenDX yourself.
However, you said that you were able to start dxFoam. So why don't you use it?

dxFoam simple

The above line will load the first case found in your current directory (check this thread for some more informations on postFoam.net and simple.net or send me an e-mail).

Dragos

[hjasak]

Hello Alex,

Have a look at the end of your configure.log file. You are probably missing some tools (eg. flex) or some header files (eg. openmotif.devel, providing Xm.h). This is why your configure failed - the log file will tell you PRECISELY what happened.

Once you install all the missing tools and headers on your computer, ./configure will run smoothly... and you are half way there.

Enjoy,

Hrv

[alexandrepereira]

Dragos:

Effectivly i can start dxFoam :

root@iskandhar:~/OpenFOAM/root-1.4.1-dev/run# dxFoam postFoam
Checking path to dx ...
Checking path to dxFoamExec executable ...
Starting dx with dxFoamExec executable ...
Starting DX user interface

But when i try to open a case in my ...root-1.4.1-dev/run directory, clicking "go" in the case selection panel openDx states that the connection to the server is broken... trying with simple.net yelds the same result...

I have quit openDx, if i try again in the shell

$dxFoam simple

Dx User inter face wont even load the case panel selection and will hang...

Thanx Dragos

Alex

Hrv : I will try again this afternoon to get dx compiled in my computer...

Just tell me, does OpenDX has the same querying capabilities ( to obtain values at points lines or
planes ) that Paraview, and to a greater extent Ensight has, or Fieldview? In case i should need some kind of full featured post Proc tool what would you advise me to use...?

Thanks for your time

Alex

[alexandrepereira]

Hi Hrv,

I followed your suggestion... i installed flex package and ./configure --prefix=/home/alex/Desktop/dx --enable-shared proceeded like a charm...

Thing is that make aborted prematurely before compilation of all dx package programs...

the error message is...

creating libLIBDX.la
(cd .libs && rm -f libLIBDX.la && ln -s ../libLIBDX.la libLIBDX.la)
sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -Dlinux -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -D_GNU_SOURCE -c -o callm_xinit.lo callm_xinit.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -Dlinux -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -D_GNU_SOURCE -c callm_xinit.c -fPIC -DPIC -o .libs/callm_xinit.o
callm_xinit.c:18:19: error: Xm/Xm.h: No such file or directory
callm_xinit.c:24: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'appcontext'
callm_xinit.c:27: error: expected ')' before 'app'
callm_xinit.c:35: error: expected specifier-qualifier-list before 'XtPointer'
callm_xinit.c:40: error: expected '=', ',', ';', 'asm' or '__attribute__' before '_rihProc'
callm_xinit.c: In function '_dxf_RegisterInputHandlerX':
callm_xinit.c:51: error: 'MyEvent' has no member named 'func'
callm_xinit.c:52: error: 'MyEvent' has no member named 'data'
callm_xinit.c:52: error: 'XtPointer' undeclared (first use in this function)
callm_xinit.c:52: error: (Each undeclared identifier is reported only once
callm_xinit.c:52: error: for each function it appears in.)
callm_xinit.c:52: error: expected ';' before 'arg'
callm_xinit.c:54: error: 'appcontext' undeclared (first use in this function)
callm_xinit.c:54: error: expected ')' before 'XtInputReadMask'
make[4]: *** [callm_xinit.lo] Error 1
make[4]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec/libdx'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec/libdx'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src'
make: *** [all-recursive] Error 1

... if i wasn't such a noob in c, and linux, i would find the quirk myself...

...but i do not yet dominate gcc so as to understnd what the heck is happening here... :-(

Alex

[hjasak]

This is your error:

callm_xinit.c:18:19: error: Xm/Xm.h: No such file or directory

For me, the file lives in:

/usr/include/Xm/Xm.h

and is provided by the package:

wooster*151-> rpm -q --whatprovides /usr/include/Xm/Xm.h
openmotif-devel-2.3.0-23

Install the package, remove the complete build directory and try again.

Hrv

[alexandrepereira]

Hi again Hrv

I Installed lesstif-dev package from Ubuntu Repo... and that error no longer exists...

now make complaints like this...:

memory.c:69:23: error: linux/sys.h: No such file or directory
make[4]: *** [memory.lo] Error 1
make[4]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec/libdx'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec/libdx'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/alex/Desktop/dx-4.4.4/src/exec'

Maybe it's a noobish thing, but i don't know how to proceed...

Thanks in advance..

Alex

[dmoroian]

Hi Alex,
In my experience with OpenDX, replacing motif with lesstif is a bad choice. It will compile and it will work too, but not very well.
Now on your error: usually sys.h comes with the kernel sources. Try to install them.

Dragos