⇤ ← Revision 1 as of 2008-08-13 22:22:46
Size: 956
Comment:
|
Size: 951
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
My personal homepage proper is at [[http://cs.nott.ac.uk/~jxm]]. This is just SAGE Days related stuff: |
My personal homepage proper is at [http://cs.nott.ac.uk/~jxm]. This is just SAGE Days related stuff: |
Line 8: | Line 7: |
-- Even the latest stable version of VTK (5.0.4) makes some weird assumptions about namespaces. In order to make it compile with GCC 4.3, replace #include <string> with #include <string.h> and similarly for other C library headers. | |
Line 10: | Line 8: |
* Even the latest stable version of VTK (5.0.4) makes some weird assumptions about namespaces. In order to make it compile with GCC 4.3, replace #include <string> with #include <string.h> and similarly for other C library headers. | |
Line 11: | Line 10: |
-- Add vtk.jar to your classpath. Notice the jar file can end up in a fresh /VTK-build/, even though you have specified other build output directory. -- Add the directory where libvtkRenderingJava.so resides to your path (export to PATH seems to work just as well as -Djava.library.path=~/VTK-build/bin/ at java's command line) -- Add libmawt.so to you LD_LIBRARY_PATH in your environment (export seems to work, although -DLD_LIBRARY_PATH at java's command line does not) |
|
Line 15: | Line 11: |
* Add vtk.jar to your classpath. Notice the jar file can end up in a fresh /VTK-build/, even though you have specified other build output directory. * Add the directory where libvtkRenderingJava.so resides to your path (export to PATH seems to work just as well as -Djava.library.path=~/VTK-build/bin/ at java's command line) * Add libmawt.so to you LD_LIBRARY_PATH in your environment (export seems to work, although -DLD_LIBRARY_PATH at java's command line does not) |
|
Line 17: | Line 15: |
CategoryHomepage | CategoryHomepage |
Jakub Marecek
My personal homepage proper is at [http://cs.nott.ac.uk/~jxm]. This is just SAGE Days related stuff:
Compiling VTK:
Even the latest stable version of VTK (5.0.4) makes some weird assumptions about namespaces. In order to make it compile with GCC 4.3, replace #include <string> with #include <string.h> and similarly for other C library headers.
Using Java VTK Wrappers:
- Add vtk.jar to your classpath. Notice the jar file can end up in a fresh /VTK-build/, even though you have specified other build output directory.
- Add the directory where libvtkRenderingJava.so resides to your path (export to PATH seems to work just as well as -Djava.library.path=~/VTK-build/bin/ at java's command line)
- Add libmawt.so to you LD_LIBRARY_PATH in your environment (export seems to work, although -DLD_LIBRARY_PATH at java's command line does not)