On Thu, 25 Mar 1999, Philip Chu wrote:
Could you provide a patch for makefile.vc. Patches are a lot easier
than just providing a list of changes you made.
> I have TclBlend 1.2.2 running successfully with TclPro 1.2 on NT. The
> TclPro tree and executable names are different, so I made the following
> changes in the TclBlend makefile:
>
> TCLSH = $(TCL_DIR)\win32-ix86\bin\protclsh$(TCL_VERSION)$(DBGX).exe
> TCLLIB = $(TCL_DIR)\win32-ix86\lib\tcl$(TCL_VERSION)$(DBGX).lib
Yeah, for some reason Tcl Blend may crash if tclblend.dll is in the
same directory as the executable. I have not looked into this because
I do not use NT and I have not run into the problem myself. Why not
keep tclblend.dll in the lib directory?
> I changed BIN_INSTALL_DIR, so tclblend.dll would end up in
> win32-ix86\bin, but then I discovered that protclsh and prowish would
> get fatal Windows memory reference errors from "package require java",
> if I started tcl in the NT Command Prompt. If I started protclsh or
> prowish from the Start menu, the problem didn't occur, and the problem
> entirely disappeared when I left BIN_INSTALL_DIR alone and let the
> makefile copy tclblend.dll into a bin directory distinct from
> win32-ix86\bin. (Of course, I have to add the new bin to my PATH).
>
> Here's a clue: when I rebuilt tclblend.dll as a debug library and did
> "package require java" from protclsh80d in the command prompt, I got the
> "Warning: [pwd]/tclblend.dll exists..." message. Note I'm not explicitly
> cd'ing to win32-ix86\bin.
>
> I don't see the problem at all with the regular tcl installation on my
> Windows 98 system.
Because tcljava.jar is shared between jacl and tclblend. If you have
them both installed you only need one copy of tcljava.jar. This makes
it a lot easier to upgrade and putting it in a tclblend directory does
not really buy you anything.
> By the way, why do the tclblend.jar and tcljava.jar files end up in the
> tcl lib directory and not the lib\tclblend directory? And a nitpick:
I think that under JDK 1.1 it is java.dll while JDK 1.2 needs jvm.dll
(and others). The problem is that pkgIndex.tcl prints this message and
there is no way to tell which version version you want to load until
the load works. So if the load fails there is no way to provide a
good error message (fun huh).
later
mo
> when I had my PATH set incorrectly, the warning message I got with
> "package require java" said I needed to have java.dll on my PATH. It's
> still jvm.dll, right?
>
> --
>
> Phil Chu
> [EMAIL PROTECTED] http://www.technicat.com/
>
>
> ----------------------------------------------------------------
> The TclJava mailing list is sponsored by WebNet Technologies.
> To subscribe: send mail to [EMAIL PROTECTED]
> with the word SUBSCRIBE as the subject.
> To unsubscribe: send mail to [EMAIL PROTECTED]
> with the word UNSUBSCRIBE as the subject.
> To send to the list, send email to '[EMAIL PROTECTED]'.
> A list archive is at: http://www.findmail.com/listsaver/tcldallas/
>
----------------------------------------------------------------
The TclJava mailing list is sponsored by WebNet Technologies.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
A list archive is at: http://www.findmail.com/listsaver/tcldallas/
