Dark-Horse-Linux
/
pyrois
1
0
Fork 1
Code Issues Pull Requests Releases Activity

minor backup cleanup for mods

master
phanes 2023-04-02 02:38:20 -04:00
parent afd68110bc
commit d3548540e7
2 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Makefile
View File

@ -125,9 +125,9 @@ all:
make build_stage1 && \ make build_stage1 && \
make build_stage2 && \ make build_stage2 && \
make build_stage3 && \ make build_stage3 && \
make backup && \
make build_stage4 && \ make build_stage4 && \
make build_stage5 make build_stage5 && \
make backup && \
# Remember, before you make clean or make purge_artifacts you MUST run # Remember, before you make clean or make purge_artifacts you MUST run

9
rex.project/x86_64/components/backup/offer_backup.bash
View File

@ -72,14 +72,13 @@ function perform_backup() {
read -r -d '' msg <<-'EOF' read -r -d '' msg <<-'EOF'
This is a great stopping point for backing up the stage if you're The following prompt will ask if you'd like to back up the
debugging. The following prompt will ask if you'd like to back up the existing sysroot. This is useful for debugging, so that you don't have
existing sysroot, in case you need to start from stage 4 again for to wait for the entire cross-compilation for every change.
whatever reason, such as a build failure.
If you select yes, you will see a gzipped tarball containing the If you select yes, you will see a gzipped tarball containing the
sysroot generated in your project root. If you select no, your backup sysroot generated in your project root. If you select no, your backup
will not be created, and you'll move on to stage 4. will not be created.
If you skip the backup and something fails from here, you'll need to If you skip the backup and something fails from here, you'll need to
run "make clean" and start from the beginning. run "make clean" and start from the beginning.