Closed
Bug 716354
Opened 14 years ago
Closed 14 years ago
freetype2 detection doesn't consider cross-compiling
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla14
People
(Reporter: m_kato, Assigned: m_kato)
References
Details
Attachments
(1 file)
|
6.66 KB,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
Actually, although we use freetype2.m4, this doesn't consider cross-compiling environment. We should use pkg-config instead of.
| Assignee | ||
Comment 1•14 years ago
|
||
Attachment #587611 -
Flags: review?(mh+mozilla)
Comment 2•14 years ago
|
||
How exactly does freetype2.m4 fail with cross-compiling? AFAICS it should work, skipping the compilation check, which using pkg-config does even when not cross-compiling.
| Assignee | ||
Comment 3•14 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #2)
> How exactly does freetype2.m4 fail with cross-compiling? AFAICS it should
> work, skipping the compilation check, which using pkg-config does even when
> not cross-compiling.
when using apt-cross, freetype-config for taget isn't installed. So it is no way to get freetype-config for target.
Comment 4•14 years ago
|
||
Shouldn't it be there, though?
Comment 5•14 years ago
|
||
Comment on attachment 587611 [details] [diff] [review]
fix
My fear is that we'd be lacking the extra tests from freetype2.m4, but I think it's fine anyways.
Attachment #587611 -
Flags: review?(mh+mozilla) → review+
| Assignee | ||
Comment 6•14 years ago
|
||
Whiteboard: [inbound]
Comment 7•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Target Milestone: --- → mozilla14
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•