Closed
Bug 487234
Opened 16 years ago
Closed 16 years ago
Strip headers from packaged frameworks
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino2.0
People
(Reporter: stuart.morgan+bugzilla, Assigned: stuart.morgan+bugzilla)
Details
Attachments
(1 file)
2.68 KB,
patch
|
mark
:
superreview+
|
Details | Diff | Splinter Review |
All of our 3rd-party frameworks have headers in them, which are useless to ship. We should run a final pass over Camino.app in our build that nukes the headers.
Assignee | ||
Comment 1•16 years ago
|
||
Every ~100 KB helps!
Attachment #374621 -
Flags: superreview?(mark)
Comment 2•16 years ago
|
||
Comment on attachment 374621 [details] [diff] [review]
fix
sr=me with changes.
>Index: Camino.xcodeproj/project.pbxproj
> 3F44AF9405BDFBA000CB4B08 /* Frameworks */,
I would do this for both app targets, not just the static one.
>Index: scripts/strip-headers.sh
>+find "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}" -name *.h -exec rm {} \;
I mighta left this out and done "rm -rf" instead of "rmdir" on the directory removal.
>+find "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}" -name Headers -type l -exec rm {} \;
>+find "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}" -name Headers -type d -exec rmdir {} \; -prune
You should look for PrivateHeaders in addition to Headers.
IM me if you want me to look at another round.
Attachment #374621 -
Flags: superreview?(mark) → superreview+
Assignee | ||
Comment 3•16 years ago
|
||
(In reply to comment #2)
> I would do this for both app targets, not just the static one.
Done (I went back and forth on that myself)
> I mighta left this out and done "rm -rf" instead of "rmdir" on the directory
> removal.
Per IM discussion, I lack mento's cast-iron stomach, but we worked out a compromise involving failing if an rmdir fails.
> You should look for PrivateHeaders in addition to Headers.
Done.
Landed on cvs trunk with those changes.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → Camino2.0
You need to log in
before you can comment on or make changes to this bug.
Description
•