> On 6 Jun 2008 John Tytgat wrote: > > In message > alan buckley wrote: > >> I'm looking into creating RISC OS packaging project packages >> for the run time components to be placed on the autobuilder >> site. >> >> I was wondering if there was somewhere in the GCCSDK build >> tree these version would naturally fit and if there was somewhere >> in the cross compiler env directory they could be copied to ensure that >> packages built in the autobuilder can request the correct dependencies. >> >> Has anyone any ideas? >> >> The base packages will be: >> >> UnixLib - this stores the SharedUnixLibrary >> SharedLibs - just the SOManager and dynamic loader >> DRenderer - Digital renderer module >> >> Note: These all have versions that should be independent of the >> current GCCSDK version as they do not change with every >> release. > > DRenderer is definately the odd one out. Currently the code is still > in BASIC Assembler format so we're doing binary releases atm (i.e. we don't > compile from source). Moreover, the stub for DRenderer is AOF. > > Currently the other components you've listed above are part in the gccsdk > build. Do you see as something which needs to be changed ?
I don't see any reason to build them anywhere else, I just don't think it's worth shipping a new package. i.e. it would still get built, but you wouldn't update the package site with them unless the module versions changed. In fact they shouldn't be updated unless the module versions are changed. > > Otherwise I would do the packaging of those as part of create-gcckit > (which would also do the packaging of !GCC and the shared libraries part > of the GCCSDK build process). Incidently I think create-gcckit is in > a need of a revamp IMHO and if you share my view on making RiscPkg packaging > of those components part of create-gcckit, we could elaborate a bit further > on this point. I'm initially adding a separate script for the riscpkg build, but I see no reason that it shouldn't be included it in create-gcckit once any problems are ironed out. I agree create-gcckit should be revamped as it took me a while to figure out what I needed to do to be able to create packages. > >> I will also need to be able to get the current package version >> numbers of the Shared Libraries C and C++ run times from the >> autobuilder. > > libunixlib 5.0.0 + libgcc_s 1 + libm 1.0.0 > libstdc++ 6.0.8 > ld 1.9.9 > I was wondering if there was a way to get these version when packaging or using the autobuilder. i.e. is there any where I can look to see what the current versions are? Or can the build be modified to store them so I can find them later? Regards, Alan _________________________________________________________________ http://clk.atdmt.com/UKM/go/msnnkmgl0010000007ukm/direct/01/ _______________________________________________ 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
