Closed
Bug 1311615
Opened 9 years ago
Closed 9 years ago
Building with gyp should copy headers, libs, executables to the right directory
Categories
(NSS :: Build, defect)
NSS
Build
Tracking
(Not tracked)
RESOLVED
FIXED
3.28
People
(Reporter: ttaubert, Assigned: ttaubert)
References
Details
Currently, we copy libraries and executables to ../dist/$OBJDIR/{bin,lib}/ with a few calls to find, in build.sh. Header files aren't copied at all. We should restore the current structure we get when using make.
(Also, the find commands don't work on OS X.)
Assignee | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #1)
> https://nss-dev.phacility.com/D104
is it expected that this link leads to a login page ?
Assignee | ||
Comment 3•9 years ago
|
||
Yeah, we're still working on a proper integration of Phabricator, unfortunately. Here's the patch:
https://gist.github.com/ttaubert/73d7c9133368c7545f624617d75aad1f
Comment 4•9 years ago
|
||
bug 1308463 was intended to cover this, but we can just make that about .chk files.
Assignee | ||
Comment 5•9 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #4)
> bug 1308463 was intended to cover this, but we can just make that about .chk
> files.
SGTM, we definitely should move that into gyp.
Assignee | ||
Comment 6•9 years ago
|
||
Comment 7•9 years ago
|
||
This is going to muck up my Firefox build integration a bit, I special-case copies that go to `$PRODUCT_DIR/dist` to convert them to `EXPORTS`:
http://hg.mozilla.org/users/tmielczarek_mozilla.com/mc/file/51db8bc7f380/python/mozbuild/mozbuild/frontend/gyp_reader.py#l98
Assignee | ||
Comment 8•9 years ago
|
||
What's the best way to handle this? Do you want to adapt gyp_reader.py after NSS merges? Can we somehow change our config to not break your integration?
Assignee | ||
Comment 9•9 years ago
|
||
Assignee | ||
Comment 10•9 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.28
You need to log in
before you can comment on or make changes to this bug.
Description
•