The response you got for "eval exec ..." doesn't give one much to go
on. Try starting dx like the following and see what you get as a
response.
dx -mdf /usr/local/dx/samples/program_guide/hello.mdf -exec
/usr/local/dx/samples/program_guide/dxexec -edit -echo
That should give you more. Loading the module after starting dx will
only work with the outboard module unless you disconnect from the
exec and restart it with the new one.
What system are you on that is returning Linux instead of linux? Can
you give the output of uname -a?
David
Hi David,
Thank you for your reply. Although loading the Hello from the
command line doesn't work, I managed to load it from the menu "Load
Modules" in DX. But I still want to figure it out in the command
line.
The following is what I got from you advice. It would be great if
you can take a look and give me some more advice.
David Thompson wrote:
You may want to give it a full path to the exec.
It doesn't work.
You may also gain more info from adding an -echo flag and see
exactly what the commands are doing to make sure things are getting
passed around correctly.
I got:
dx -mdf /usr/local/dx/samples/program_guide/hello.mdf -exec
/usr/local/dx/samples/program_guide/dxexec -echo
eval exec "/usr/local/dx/bin_linux/startupui"
I have no idea whether this is correct or not. But "dx -echo" gives
the same response.
Another thing which may be worth mentioning is that "echo $ARCH"
returns "Linux", but the default linux arch setting is "linux". So
when I rebuilt OpenDX, it created a directory "bin_Linux". Because
"dx" command looks for the "bin_linux", I copied bin_Linux to
bin_linux. I did the same thing to lib_Linux. Is this inconsistency
a possible reason for the failure of loading Hello?
Thank you.
Jian
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
