Re: kitgen with packages - KBS

On 16 Apr 2007, at 13:43, rene wrote:

>>> new (may be this get better):
>>>   cd [file dirname [info nameofexe]]/../..
[...]
> I am building in the same directory as before but using a different
> executable, the "tclsh.." from the build directory.

Ah, of course.  No need to build kitgen just for building extensions.

> Now some remarks to specific extensions:
>
> "kbs.tcl build Itk" failed in
>   Sources symlink [Srcdir]/../Itcl-[Version]
> could not create new link ".../kitgen/sources/Itk-3.3": target ".../
> kitgen/sources/Itk-3.3/../Itcl-3.3" doesn't exist
>
> workaround in itk.kbs:
> #Sources symlink [Srcdir]/../Itcl-[Version]
> Sources cvs incrtcl.cvs.sourceforge.net:/cvsroot/incrtcl incrTcl

Strange.  Didn't the "Requires Itcl" rule in Itk.kbs force a download  
& build of Itcl, just before the Sources command ran?

But yes, this is simpler, I don't expect it to happen often that a  
single download gets used to build two different extensions - and the  
extra space use is insignificant.

> Tkhtml
>   fetching /home/rene/devel/test/kitgen/downloads/tkhtml3-
> alpha-14.tar.gz
> gzip: /home/rene/devel/test/kitgen/downloads/tkhtml3-alpha-14.tar.gz:
> not in gzip format
>  --> 1230545 byte
>
> mmh..? If I fetch the file by hand it works?
>  wget http://tkhtml.tcl.tk/tkhtml3-alpha-14.tar.gz --> 821190 byte

Strange indeed.  I suspect a mime-type problem on the tkhtml website.

> trofs:
> checking system version (for dynamic loading)... /home/rene/devel/ 
> test/
> kitgen/sources/trofs-0.4.3/configure: line 10146: syntax error near
> unexpected token `('
> /home/rene/devel/test/kitgen/sources/trofs-0.4.3/configure: line
> 10146: `    case `(ac_space=' '; set | grep ac_space) 2>&1` in'
> child process exited abnormally
>
> workaround in "sources/trofs-0.4.3/configure (line 7145):
> old:
>                 system=MP-RAS-`awk '{print }' /etc/.relid'`
> changed:
>                 system=MP-RAS-`awk '{print }' /etc/.relid`

Good catch.  Am CC'ing Don Porter so he hears about this problem.

> With the above errors in mind I would vote for a repository with
> patched and ready to go versions.

Good point.  This will depend on the scale and time-scale over which  
kbs is intended to be used.  We may be moving towards a full-scale  
build system plus repository - I haven't yet decided what sort of  
commitment I'm willing to make towards such a service.

-jcw