Changes between Version 3 and Version 4 of other/xnbody

Timestamp:

02/05/10 10:47:24 (14 years ago)

Author:

Mathias Winkel

Comment:

--

other/xnbody

@@ -194 +194 @@
  1. First, the VTK installation: If there is another QT installation available on the machine, ccmake may not find the right one. Lucky developers get a chance to specify the right version the QT-step by choosing the right include file and qmake executable (which is more important!). Check your environment variables!
  1. If xnbody will not come up: Double-check your VTK installation for missing ONs or wrong QT paths. If everything is ok here, try to copy the source files into the build directories (but do not count on this!) and rebuild VTK. After this, you have to remove the build-directory ~/programs/xnbody completely, because a simple  "make clean"  misses this point! Sometimes running qtconfig in ~/programs/qt4/bin can give a hint, too. Try to check OpenGL by running glxgears. But this problem is still unsolved, so keep trying! 
+ 1. Another possibility if xnbody does not start after invocation is a possible problem with your LD_LIBRARY_PATH variable during make install, hence the shared libraries are not found. As a solution empty your LD_LIBRARY_PATH before compiling xnbody, hence in your xnbody-directory invoke
+{{{
+#!sh
+make clean
+export LD_LIBRARY_PATH=""
+make
+make install
+}}}
  1. Back to VTK: If you have to reinstall VTK it is essential to remove everything ccmake left in the source directory. Otherwise there may occur strange conflict  situations. The easiest way is to delete the VTK source directory and untar it again.
  1. Running XNBODY: If XNBODY does not connect to your seapserver, check your firewall for the listen-port you have specified in .visitrc