Modify build setup to only build crypto pieces when specifically requested

RESOLVED FIXED in 0.5

Status

Cloud Services
Firefox Sync: Build
RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: mconnor, Assigned: mconnor)

Tracking

unspecified
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

9 years ago
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?

Comment 1

9 years ago
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
(Assignee)

Comment 2

9 years ago
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. ;)
(Assignee)

Comment 3

9 years ago
Need this to make automated builds easier, taking.
Assignee: nobody → mconnor
(Assignee)

Updated

9 years ago
Depends on: 503429
(Assignee)

Updated

9 years ago
Component: General → Build Config
QA Contact: general → build-config
(Assignee)

Comment 4

9 years ago
Fixed by bug 503429
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED

Updated

8 years ago
Target Milestone: 1.0 → 0.5
You need to log in before you can comment on or make changes to this bug.