I took a look at the build script. the script it self doesnt show that it ever exhibited that behavior. and if it did and i missed it, there was nothing changed that would cause that. unless there is another file that would cause this change.
i havent built with that command but you might want to try using the one on that website right above it. or if you want to make it do it all at once make a script of your own that calls the build.sh moves the kernel and then calls brunch... just a thought.
also to the guy who said that there was no 4/14 nightly... so?
Thanks for looking at that man. You just kinda reminded me that I have a VM from a few days ago that does the kernel compile & then builds that I can use to compare to the new one I've been using.
---------- Post added at 07:41 PM ---------- Previous post was at 07:04 PM ----------
Well, after comparing the files - it definitely was changed, probably to make the process better/streamlined.
The old code when building:
Code:
# Start the Build
case "$ADDITIONAL" in
kernel)
echo -e "${txtgrn}Building Kernel...${txtrst}"
cd kernel/samsung/${board}
./build.sh "$COMMAND"
cd ../../..
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
;;
*)
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
;;
esac
and the new code:
Code:
# Start the Build
case "$ADDITIONAL" in
kernel)
echo -e "${txtgrn}Rebuilding bootimage...${txtrst}"
rm -rf out/target/product/${COMMAND}/obj/KERNEL_OBJ
rm out/target/product/${COMMAND}/kernel
rm out/target/product/${COMMAND}/boot.img
rm -rf out/target/product/${COMMAND}/ramdisk*
make -j${THREADS} out/target/product/${COMMAND}/boot.img
;;
*)
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
;;
esac
It seems to be exiting the case before it gets to
Code:
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
as it does output the elapsed time (which code is after the case statement), but does not echo "Building Android..." and does not do a brunch. Unfortunately I'm not strong enough with programming to figure out why it is exiting
. I'm sure someone else can see it plain as day.
Interestingly enough, I've also found that during the build of 'new' kernel, for some reason it decides to use the prebuilt kernel instead:
Code:
uild/core/tasks/kernel.mk:26: ***************************************************************
build/core/tasks/kernel.mk:27: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:28: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:29: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:30: * source repository to kernel/samsung/i777
build/core/tasks/kernel.mk:31: * See http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building
build/core/tasks/kernel.mk:32: * for more information *
build/core/tasks/kernel.mk:33: *************************************************
Maybe because of the deprecated commands? Either way, apparently using "./build.sh i777 kernel" no longer compiles the kernel OR builds android.
EDIT: After looking at it, I realized...shouldn't Build Android lines be directly after the
"make -j${THREADS} out/target/product/${COMMAND}/boot.img"?
Something similar to:
Code:
# Start the Build
case "$ADDITIONAL" in
kernel)
echo -e "${txtgrn}Rebuilding bootimage...${txtrst}"
rm -rf out/target/product/${COMMAND}/obj/KERNEL_OBJ
rm out/target/product/${COMMAND}/kernel
rm out/target/product/${COMMAND}/boot.img
rm -rf out/target/product/${COMMAND}/ramdisk*
make -j${THREADS} out/target/product/${COMMAND}/boot.img
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
;;
*)
echo -e "${txtgrn}Building Android...${txtrst}"
brunch ${brunch}
;;
esac
since the second "Building Android" command is part of the 'else' part of the case statement? This is why I didn't become a programmer haha ::facepalm::
