Hello,
while playing around with my new laptop, I noticed a bug in the current
build system: it is possible to get a nasty mix-up of Tcl versions
resulting in a failed build. Here is the scenario I found this with:
- I have Tcl 8.4 and 8.5 installed. The command "tclsh" starts the
Tcl 8.4 shel
Cmake code tends to do this kind of thing by searching through directories
in decreasing version order. I think the "correct" thing to do is
1) Find tclsh
2) Find the version of tcl associated with it
3) Only search in directories with that version number
I've also been bitten by this mysel
Hi, everyone,
Thanks for all your help and ideas. I think I have solved this
mystery. The symptoms are very misleading and confusing, but the
underlying cause turns out to be fairly easy to understand.
The problem is actually related to command line parsing. It turns
out that C programs
On Jan 27, 2010, at 16:42 , David MacMahon wrote:
> 3a. Add code within "#if define ( __APPLE __)" blocks so that NXArgc
> can be modified to match the modified contents of NXArgv/argv. This
> might also an issue on NeXTSTEP, since I think that's where Apple
> picked up these variables (hence th
Hi David,
that is a remarkable piece of detective work. I have never used OSX
myself and therefore do not have any experience developing applications
for it, but you have digged up is a rahter nasty feature here.
As for sending patches, you can do that to this list, unless it is
a rather large pa
Hi Andrew,
I solved the issue by using the macros TCL_MAJOR_VERSION and
TCL_MINOR_VERSION. That way building the Tcl/Tk bindings for PLplot
is independent of the version of tclsh, but instead relies exclusively
on the Tcl include files.
Regards,
Arjen
On 2010-01-27 17:37, Andrew Ross wrote:
>
