Ideally, the crypto component would be a part of the platform. Until then, it'd be a win for getting up and running to only rebuild the crypto pieces if we specifically request it (i.e. |make crypto| or something). The component only changes if we add platforms, and other than that we shouldn't need to make people deal with the SDK. I might even go as far as to say we should move that code into a /crypto subdirectory and leave it out of the toplevel makefile entirely. Thoughts?
Would save me a step ;) Right now I build weave with.. make xpi && hg revert -a --no-backup platform Plenty of accidental checkins of a rebuilt binary.. http://hg.mozilla.org/labs/weave/log/tip/platform/Darwin/components/WeaveCrypto.dylib
I'm currently just commenting out the two lines at: http://mxr.mozilla.org/labs-central/source/weave/Makefile#111 to avoid the same fate. ;)
Need this to make automated builds easier, taking.
Assignee: nobody → mconnor
Component: General → Build Config
QA Contact: general → build-config
Fixed by bug 503429
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Component: Firefox Sync: Build → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.