Closed
Bug 371201
Opened 19 years ago
Closed 19 years ago
error on spaces in XPI_NAME and some other Makefile vars
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ted, Assigned: ted)
References
()
Details
Attachments
(1 file, 2 obsolete files)
|
942 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
This can cause us to break with unhelpful error messages like:
/bin/sh: ../../dist/xpi-stage/gban: File exists
make[1]: *** [libs] Error 1
make: *** [all] Error 2
| Assignee | ||
Comment 1•19 years ago
|
||
I didn't test this, but it's pretty simple. We might even consider erroring if XPI_NAME is set but contains spaces.
Attachment #255988 -
Flags: review?(benjamin)
Comment 2•19 years ago
|
||
(In reply to comment #1)
> Created an attachment (id=255988) [details]
> strip XPI_NAME
>
> I didn't test this, but it's pretty simple. We might even consider erroring if
> XPI_NAME is set but contains spaces.
>
I've tested this and it works.
Comment 3•19 years ago
|
||
Comment on attachment 255988 [details] [diff] [review]
strip XPI_NAME
After discussion on IRC, we're going to try and create a meaningful error if various important variables have extraneous spaces. This might be hard ;-)
Attachment #255988 -
Flags: review?(benjamin) → review-
| Assignee | ||
Updated•19 years ago
|
Summary: strip trailing spaces from XPI_NAME when setting FINAL_TARGET → warn on trailing spaces in XPI_NAME (breaks FINAL_TARGET)
| Assignee | ||
Comment 4•19 years ago
|
||
This checks XPI_NAME for internal or trailing spaces. Are there other vars you think we should sanity check while I'm doing this?
Attachment #255988 -
Attachment is obsolete: true
Attachment #256032 -
Flags: review?(benjamin)
Comment 5•19 years ago
|
||
Comment on attachment 256032 [details] [diff] [review]
warn if spaces or trailing spaces in XPI_NAME
LIBRARY_NAME
MODULE
DEPTH
SHORT_LIBNAME
XPI_PKGNAME
INSTALL_EXTENSION_ID
You can probably shorten this to:
$(if $(filter-out 0 1,$(words $(XPI_NAME))),$(error Spaces are not allowed in XPI_NAME))
And then you could do a $(foreach) to do that for a bunch of variables. Though... that's not pretty.
Attachment #256032 -
Flags: review?(benjamin) → review-
| Assignee | ||
Comment 6•19 years ago
|
||
Okay, this checks all the vars that bsmedberg mentioned, and uses a slightly modified version of his filter-out example to do so.
Attachment #256032 -
Attachment is obsolete: true
Attachment #259684 -
Flags: review?(benjamin)
Comment 7•19 years ago
|
||
Comment on attachment 259684 [details] [diff] [review]
check a bunch of variables
>Index: config/config.mk
>+CHECK_VARS := XPI_NAME \
>+ LIBRARY_NAME \
I think we should standardize on a whitespace strategy, and I'd prefer
SETVAR = \
THING1 \
THING2 \
$(NULL)
We would only use spaces where absolutely required by rule syntax, and if we change the name of a variable we don't end up changing the spacing.
Other than that, r=me. Thanks.
Attachment #259684 -
Flags: review?(benjamin) → review+
| Assignee | ||
Comment 8•19 years ago
|
||
Checked in with that fix.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Summary: warn on trailing spaces in XPI_NAME (breaks FINAL_TARGET) → error on spaces in XPI_NAME and some other Makefile vars
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
•