In article <alpine.DEB.2.22.394.2110151354320.3902245@thelappy>, Rhett Aultman <rh...@rhettaultman.com> wrote:
> On Fri, 15 Oct 2021, David Pitt wrote: > > Nettle has just built here on the autobuilder but libsssh2 had to be built > > first. > Ah! I wasn't aware that it build through the autobuilder. I've noticed > that the autobuilder tends to download checkpointed sources and clean up > after itself following building, so I'm curious if there are ways to use > it as an environment more friendly to active development and iteration? > Apologies if these are basic questions to ask; I really did try to educate > myself through the wiki first. Adding the '-D' option to the build command will leave the folder in place after building, Any dependencies should also get built automatically. ../autobuilder/build -v nettle -D Assuming there's a build-setvars file with similar to below in the folder the build command is run from. GCCSDK_INSTALL_CROSSBIN=<path to autobuilder>/cross/bin GCCSDK_INSTALL_ENV=<path to autobuilder>/env RO_SHAREDLIBS=no AB_ELFBUILD=yes Then build with, <path to autobuilder>/env/ro-make -f GNUmakefile _______________________________________________ GCCSDK mailing list gcc@gccsdk.riscos.info 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
