In message <[EMAIL PROTECTED]>
Peter Naulls <[EMAIL PROTECTED]> wrote:
> John, the !GCC application files from riscos/dist are not populated in
> release-area/full until create-gcckit is run. Wouldn't it make more
> sense to do this during the build-it riscos phase? I don't need
> to pack it all up just to run !GCC over NFS or copy it to a
> RISC OS machine.
Yes and this is a bit elaborating on what I mentioned on 'create-gcckit' in
<URL:http://www.riscos.info/pipermail/gcc/2008-June/004414.html>.
It would indeed be a good thing to end up with a snapshot which is usable
across NFS or in a structure allowing to zip it as is after a
'build-it riscos'.
But on the other hand I don't think we should just move what is happening
inside 'create-gcckit' to 'build-it' because in the case when you have to
restart the build with 'make' + 'make install' (in case it got stopped with
an error) you still need to do some of the stuff currently happening in
'create-gcckit'. And calling 'build-it' containg the 'create-gccsdk'
code is not a possibility as it will restart the build from scratch.
So the solution is obvious: 'create-gcckit' can get called at the end
of 'build-it riscos'. Note that 'create-gcckit' is doing more things than
!GCC skeleton copying before you can use the result over NFS (like
suffix swapping).
And 'create-gcckit' needs a revamp as it is not good enough IMHO. A better
approach is probably:
1. Leave 'release-area/full' directory untouched after doing what's now
done in 'build-it riscos' as this will allow us to restart based on an
existing build after small local fix (btw, not something which works
bulletproof).
2. Copy 'release-area/full' to e.g. 'release-area/full-riscos' using soft
symlinks and do the necessary suffix swapping, deleting uninteresting
files, copy 'riscos/dist/!GCC' skeleton, building the man pages etc
i.e. the stuff which 'create-gcckit' is doing. This directory is
usable via NFS on RISC OS, or you can zip it and have a fat, everything
included release.
3. Optionally, 'release-area/full-riscos' can be used to build kits (and
I believe RiscPkg can be used here). Probably be done by copying
'release-area/full-riscos' to a new directory and split the contents
on the several kits we envision to make.
John.
--
John Tytgat, in his comfy chair at home BASS
[EMAIL PROTECTED] ARM powered, RISC OS driven
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
