Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'bacon', did you mean 'racoon'?
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/builder/android-x86'
Ideas?
god why do people do this shit where they have like 40 tiered build systems going on their shit project
Use /sqt/ you retard pajeet
>>61538790
I have no Idea. No really, I just put in the command on the website but it didn't build.
>>61538790
Tell me about its out of control. Maven, Gradle, Spring , Jenkins, god knows what else
>>61538800
>/sqt
?
>>61538822
not to mention a lot of them are just wrappers into/out of make/autoconf. it's really weird man.
pajeets and their factoryfactoryfactory shit are infected god damn everything
>>61538822
>Maven, Gradle
Analogous to Make.
>Spring
A framework for writing web and muh cloud applications in Java.
>Jenkins
A build server, primarily focused on Java and Maven, but works with C++ and the various Make-likes.
>>61538762ninja.mk:151
...
$(sort $(DEFAULT_GOAL) $(ANDROID_GOALS)) : ninja_wrapper
@#empty
.PHONY: ninja_wrapper
ninja_wrapper: $(COMBINED_BUILD_NINJA) $(MAKEPARALLEL)
@echo Starting build with ninja
+$(hide) export NINJA_STATUS="$(NINJA_STATUS)" && source $(KATI_ENV_SH) && $(NINJA_MAKEPARALLEL) $(NINJA) $(NINJA_GOALS) -C $(TOP) -f $(COMBINED_BUILD_NINJA) $(NINJA_ARGS)
...
>>61538937
>>61538762Running kati to generate build-cm_android_x86.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: dependency cycle: /home/builder/android-x86/out/target/product/android_x86/kernel -> /home/builder/android-x86/out/target/product/android_x86/kernel
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/builder/android-x86'