Signing a CyanogenMod ROM while building

I build my CyanogenMod 13 ROM for the OnePlus One (bacon) as a "user" build and I always sign it with my own release-keys. I have both releasekey.x509.pem and a releasekey.pk8 already, but I take a lot of steps to sign it everytime I compile it.

Code:

---

make dist
./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs out/dist/cm_bacon-target_files-xxxxxxxxxx.zip signed-target_files.zip
./build/tools/releasetools/ota_from_target_files -k ~/.android-certs/releasekey signed-target_files.zip my_own_CyanogenMod13_ROM.zip

---

I read about adding PRODUCT_DEFAULT_DEV_CERTIFICATE to the product makefiles but I don't really understand how to do it. I want the build process to include my release keys and sign the ROM when I do:

Code:

---

brunch cm_bacon-user

---

Is it possible? Is there any way to add some more stuff to that line to let the build know that I want it to use my keys?

from xda-developers http://ift.tt/1Tyd74R
via IFTTT