| | 3 | |
| | 4 | ---- |
| | 5 | Addition (7/19/2009): |
| | 6 | |
| | 7 | This ticket is also related to #336. Maybe try to solve that first, because of it's higher priority. |
| | 8 | |
| | 9 | And another remark: The irk package (tcl8.x/irk) is also a custom package and doesn't belong to the native Tcl library. This package is loaded in the following way: |
| | 10 | {{{ |
| | 11 | package require irk |
| | 12 | }}} |
| | 13 | Therefore we MUST adjust the Tcl library path so it will still find the custom packages (which is more than just a bunch of scriptfiles). |
| | 14 | |
| | 15 | You also have to adjust the execution path, because right now the interpreter uses the path to the Orxonox binary, which makes it impossible to use relative paths in the Tcl scripts (for example remote.tcl fails at the moment). |