[Tickets] [Orxonox] #314: Move tcl scripts to a separate folder

Orxonox trac at orxonox.net
Sun Jul 19 03:52:01 CEST 2009


#314: Move tcl scripts to a separate folder
--------------------------+-------------------------------------------------
 Reporter:  rgrieder      |        Owner:  nobody                         
     Type:  defect        |       Status:  new                            
 Priority:  high          |    Milestone:  Version 0.2 Codename: Bellatrix
Component:  ScriptEngine  |      Version:  0.2.0                          
 Severity:  normal        |   Resolution:                                 
 Keywords:  tcl           |  
--------------------------+-------------------------------------------------
Changes (by landauf):

  * component:  Cmake => ScriptEngine

Old description:

> You can find three Tcl scripts in the media/tcl8.# directory where # is
> either 4 or 5. They don't really belong there and should be put in a
> folder like media/tcl-scripts. It also saves the redundancy.[[br]]
> Unfortunately this involves telling Tcl somehow where to find the
> scripts. There is already a tcl lib path set somewhere to media/tcl-8.#
> but that it should really only point to the Tcl library directory.

New description:

 You can find three Tcl scripts in the media/tcl8.# directory where # is
 either 4 or 5. They don't really belong there and should be put in a
 folder like media/tcl-scripts. It also saves the redundancy.[[br]]
 Unfortunately this involves telling Tcl somehow where to find the scripts.
 There is already a tcl lib path set somewhere to media/tcl-8.# but that it
 should really only point to the Tcl library directory.

 ----
 Addition (7/19/2009):

 This ticket is also related to #336. Maybe try to solve that first,
 because of it's higher priority.

 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:
 {{{
 package require irk
 }}}
 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).

 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).

-- 
Ticket URL: <http://www.orxonox.net/ticket/314#comment:3>
Orxonox <http://www.orxonox.net>
Orxonox Open Source game


More information about the Tickets mailing list