Looking through this code again, the ::xotcl::lib is not really used in XOTcl's code anymore ... and given the fact that you can create some setup, where something goes wrong in searching for the xotcl lib, I would propose to remove the warning message ... that would require the following patch (for 1.0.3) in generic/predefined.xotcl:
@@ -351,7 +351,7 @@ }
if {![info exists success]} { - puts stderr "Cannot locate the XOTcl library on your system!" - return 0 + #puts stderr "Cannot locate the XOTcl library on your system!" + return }
The thing that happens then, if the lib is not found, is that it is reset to the compiled-in default ... which is ok, I think.
--uwe
On Monday 12 May 2003 19:20, MichaelL@frogware.com wrote:
I'm using XOTcl under both Tcl 8.4.2 and AOLServer. Here's my Tcl 8.4.2 setup.
$auto_path is {d:/appsdev/tcl/lib/tcl8.4 d:/appsdev/tcl/lib} both before and after
package require XOTcl 1xotcl is installed under d:/appsdev/tcl/lib/xotcl-1.0.2.
In that dir is a pkgIndex.tcl file with the following:
package ifneeded XOTcl 1.0 [list load [file join $dirwin/Release/xotcl1.0.dll] XOTcl]
xotcl1.0.dll is under d:/appsdev/tcl/lib/xotcl-1.0.2/win/Release.
I've also tried placing the dll in the bin directory and adjusting the pkgIndex.tcl file accordingly, but it had the same result.
As I said, the dll does in fact load, and I can use XOTcl (and all of its libraries and samples). The problem is just the message.
Uwe Zdun uwe.zdun@wu-wien.ac.at wrote on 05/12/2003 11:28:52 AM:
hmm ... Can you provide a bit more detail? where have you installed
xotcl?
from where do you run it? what is the setting of the variable auto_path
(
use: puts $auto_path at the beginning your program)?
Uwe
On Monday 12 May 2003 16:35, MichaelL@frogware.com wrote:
With XOTcl 1.0.2 on Windows 2000 I get the "Cannot locate the XOTcl library on your system!" message despite the fact that the library is successfully found. I read the message in the archives on this, but a)
the
workaround didn't seem to work for me (if I understood it correctly)
and
b) it seemed like 1.0.2 was supposed to fix the problem (but obviously didn't in my case).
-- Uwe Zdun Department of Information Systems, Vienna University of Economics Phone: +43 1 313 36 4796, Fax: +43 1 313 36 746 zdun@{xotcl,computer,acm}.org, uwe.zdun@wu-wien.ac.at