JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for STARDEV Archives


STARDEV Archives

STARDEV Archives


STARDEV@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

STARDEV Home

STARDEV Home

STARDEV  July 2004

STARDEV July 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: tclsys

From:

Norman Gray <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Wed, 21 Jul 2004 21:40:52 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

Tim,

On 2004 Jul 21 , at 20.02, Tim Jenness wrote:

>>>  2. itcl should be included in the search (with corresponding
>>> variables)
>>>     I assume an ITCL_LIBS should be set but there won't be a need
>>>     for ITCL_CFLAGS since they should be shared. The question is
>>> whether
>>>     the optional status of iTCL is a problem or whether
>>> STAR_PATH_ITCLTK
>>>     needs to be created which uses required itcl, tcl and tk all to
>>> be
>>>     in the same place. Should there be a STAR_PATH_TCL which doesn't
>>> worry
>>>     about TK (but which starts looking in the default Starlink
>>> location).
>>
>> It still sets TCL_CFLAGS and TCL_LIBS with the required flags.  I
>> haven't created separate TCL, TK and ITCL variables, because (a) it
>> starts to get confusing, and (b) extra flags wouldn't hurt, so there's
>> no need to avoid including some flags, so no utility in having
>> separate
>> variables.  Anyone disagree?
>
> Does it get confusing that TK_LIBS would be used for linking tk apps?

Well, a bit, since there would be TCL_CFLAGS and TCL_LIBS, but a
TK_LIBS without a corresponding TK_CFLAGS, unless it were either empty
or contained just the flag for the required X includes, and I'm not
sure what there would be for itcl.  Come to think of it, perhaps a null
TK_CFLAGS wouldn't be a problem.  Perhaps that's best.  OK, I'll do
that.

>> Having said that, I don't know what I'm supposed to be testing for in
>> itcl.  There isn't an itclConfig.sh, nor any lib directory which has
>> to
>> be added to a -L flag, and so the itcl test doesn't actually do
>> anything.  Any clues?
>>
>
> There is an itkConfig.sh which specifies libitk. I assume this means
> itcl
> is a Tk extension rather than just a tcl extension. (ie an itcl app
> must
> always be linked against libtk).

I've just found an itkConfig.sh in the itcl build tree, which is
configured (from .in) but not installed, and after grepping around the
rest of my system for *Config.sh, I've found an itclConfig.sh.in which
isn't even configured, much less installed.  Is something terribly
broken with the itcl distribution we have?

> I sense oddles of pent up frustration.

Programming in oodles of portable-sh has lost its minimalist charm.

Norman


--
----------------------------------------------------------------------
Norman Gray  :  Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/  :  www.starlink.ac.uk

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
January 2023
December 2022
July 2022
June 2022
April 2022
March 2022
December 2021
October 2021
July 2021
April 2021
January 2021
October 2020
September 2020
August 2020
May 2020
November 2019
October 2019
July 2019
June 2019
February 2019
January 2019
December 2018
November 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
December 2017
October 2017
August 2017
July 2017
May 2017
April 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
2004
April 2003
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager