hello friends,
i have been trying to install tclBlend on an intel m/c running solaris.
i have already
installed jdk1.2 and tcl8.2.1 on my machine. i had to download the
source code
for tclBlend1.2.5 as binaries are not available for intel platform.
otherwise installing
binaries would have been a
Try using the configure and makefile script at the top
level (the TEA makefiles):
cd tclblend
configure --with-tcl...
make
Which version of gcc do you have?
Do you have JDK 1.2.2+, or less than that?
It almost appears that something in the JDK .h files is not
getting picked up, as if there is
We do not provide much support for pre-compiled binaries
for a number of reasons. We do give out Windows binaries,
but that is just because windows dev tools are not free
and they kind of suck (IMHO). It seems like binaries
would make things easier, but in fact the opposite is
true.
At any rate,
All,
I have 2 questions.
1. I am trying to familiarize myself with Jacl so that I
may use it for regression testing. It looks very promising
and at Mo's suggestion, I downloaded the Jacl source so that
I could use the tests in that package as a template. However,
when I source any of the tes
Hi all.
I am looking over my todo list for the next "stable" release of Tcl
Blend (1.2.6) and I am wondering if we should move up to Tcl 8.3
for the pre-compiled Windows binaries.
I am NOT saying that the source code for the 1.2 version would be changed
to only support 8.3, just the pre-compile
If you want to run the regression tests you would typically
run "make test" in the build directory. Under windows you
need to run "nmake -f makefile.vc test". That will build
the .class files like tcl.lang.JavaTestExtension and source
each of the regression tests for you. If you want to run them
b
It's too bad that we can't make TclBlend stubs enabled,
that would fix this. The problem with stubs is that
the TclBlend DLL can also be used as a shell, and shells
cannot use stubs (unless they located and load the
Tcl DLL). Since Jiang Wu seems to have fixed this feature
(using TclBlend as a s
On Tue, 4 Apr 2000, Scott Redman wrote:
I thought the other problem with stubs was that one tclblend.dll
could not be loaded into both a JDK 1.1 and a JDK 1.2 JVM.
> It's too bad that we can't make TclBlend stubs enabled,
> that would fix this. The problem with stubs is that
> the TclBlend DLL
Title: RE: [Tcl Java] Should Tcl Blend 1.2.6 use Tcl 8.2 or Tcl 8.3?
I'd agree with going to Tcl 8.3 for the binary releases now. The main people this might inconvenience are those who rely on the free parts of TclPro as an easy way to get Tcl/Tk/IncrTcl/Iwidgets/etc..., but since you can pic
> I thought the other problem with stubs was that one tclblend.dll
> could not be loaded into both a JDK 1.1 and a JDK 1.2 JVM.
The JDK issue is separate. The Tcl stubs mechanism only
helps you with the Tcl (and Tk) DLLs, not with the JDK
DLLs. We will still need to build separate versions for
Sorry folks, I never send the TclBlend patch to this mailing list. I just
checked the Scriptics bug DB. My bug report is there now. It is number
4352. The report does not show the patch. I copied the bug report at the
end of this email. The patch is also attached to the email. The patch
all
> > Nope, no "feature changes" are going into 1.2.6. I still have some
> > error message improvements that I want to add before 1.2.6
> > will go out but there are no features that need to be changed (IMHO).
> > A compiler switch for stubs might be a good thing to add to 1.3.
It might be easy, bu
12 matches
Mail list logo