Closed
Description
Currently there are some recipes with hardcoded job count which will probably cause issues if the build is run on a toaster-like machines (such as one of my old machines' N270 + 1GB RAM). While the solution with multiprocessing.cpu_count is nice, it'd be much better if we had an option for the user to specify the jobs and then fallback to cpu_count value by default. Otherwise if I run it like this, my session resources' might be just hijacked by p4a and on that particular CPU it's really bad if I want e.g. to run e.g. latest firefox with multiple tabs while building some app.
https://github.com/kivy/python-for-android/search?q=-j4&unscoped_q=-j4&type=Code
https://github.com/kivy/python-for-android/search?q=-j5&unscoped_q=-j5&type=Code