I have recently noticed that during C-C TB build that
a bunch of PEM certificates seem to be created during BUILD.
That is fine in itself.
However, it seems to be invoked at each(?) invocation of subsequent
build after a minor modification of the source files (not related to PEM
creation). It adds to the total build time and when I change only a line
of a source file and try re-building, this hurts.
Has anyone noticed this?
cf. I am using -j4 and -s flags to make and I saw, for example, the
following lines in one build:
ca-all-usages.pem
ca-missing-keyCertSign.pem
ca.pem
ee-EKU-CA-int-EKU-CA.pem
ca-no-keyUsage-extension.pem
ee-EKU-CA-int-EKU-CA_EP.pem
ca.pem
ee.pem
ee-keyCertSign-and-keyEncipherment-ca-all-usages.pem
ee-EKU-CA-int-EKU-CA_EP_NS_OS_SA_TS.pem
int.pem
ee-keyCertSign-and-keyEncipherment-ca-missing-keyCertSign.pem
ee-EKU-CA-int-EKU-CA_NS.pem
ee-keyCertSign-and-keyEncipherment-ca-no-keyUsage-extension.pem
ee-EKU-CA-int-EKU-CA_OS.pem
ca.pem
ee_int-v1-BC-cA.pem
... many such lines ...
These targets are again invoked on the subsequent make.
I think the operations are not cheap. I see load goes up to 2.x or
something.
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
