On Fri, 21 Apr 2023 12:41:11 -0000
John via Replicant <replicant@osuosl.org> wrote:
> On Thu, 20 Apr 2023 20:57:19 +0100 J05HYYY via Replicant wrote:
>
> > To make just the boot image:
> >
> > ./vendor/replicant/build-toolchain
> > . build/envsetup.sh
> > lunch replicant_i9305-userdebug
> > make -j1 bootimage
>
> Thanks a lot!
>
> Is there any particular reason to use '-j1' instead of utilizing the
> full potential of a multicore CPU?
I usually use -j1 because:
A) It's easier to debug linear code if you hit an error.
and
B) I've had problems compiling using all the cores on the machine, for
instance, running out of memory, crashing the environment etc. whilst
building.
It is however, as you've guess probably a bit slower, so feel free to
do whatever.
>
> Also: when I build just the boot.img, how will that work with signing?
>
> I don't quite understand the full details of the generation of the
> signing keys and the actual signing process for which I asked in a
> separate thread here on the mailing list ("How to sign at the end of
> the build process?") and hope for an answer. I am mentioning it
> because it is related.
>
> IIUC, signing a method to ensure file authenticity and system
> integrity. Currently, on the devices I have installed Replicant
> images which I downloaded from the website. I suppose they have their
> own signatures built-in. Now, when I build boot.img myself - wouldn't
> that be signed with some other, different key, thus conflicting the
> signatures of the already installed system? I don't understand the
> process and there is no documentation, so I hope you or someone else
> can clarify how to approach that correctly.
Regarding signing.
I don't sign my images. They run after flashing with heimdall without
signing. Anything I distribute, I will do so semi-anonymously, so there
is little point in me signing them. As far as I understand, signing just
shows proof of origin (unless you relock the bootloader, which I
haven't heard about w/ replicant). What I do instead is take a checksum
of the software and give that to people.
I guess if you were doing things properly (for instance under the
official 'replicant umbrella') you would want to sign to say that the
images are official and built by the replicant project.
But for 'casual use', I see little point in signing the images.
I may be completely wrong on it's usefulness however.
> _______________________________________________
> Replicant mailing list
> Replicant@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/replicant
Josh
_______________________________________________
Replicant mailing list
Replicant@osuosl.org
https://lists.osuosl.org/mailman/listinfo/replicant
