Closed
Bug 34286
Opened 25 years ago
Closed 21 years ago
Test directory dependency
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla1.1alpha
People
(Reporter: Joerg.Brunsmann, Assigned: law)
References
()
Details
(Keywords: arch)
If someone wants to build without the test directories
and ./configure --disable-tests you get a compile
error because
xpfe/bootstrap/nsSetupRegistry.cpp
depends on
webshell/tests/viewer/nsSetupRegistry.cpp
Using --disable-tests just means that the test directory isn't traversed during
the build. The source should always be there. Reassigning to xpcom registry to
see if they are interesting in changing that code.
Assignee: cls → dp
Component: Build Config → XPCOM Registry
QA Contact: cyeh → leger
Comment 2•25 years ago
|
||
All this setup registry stuff is xpfe. Bill ?
Assignee: dp → law
Target Milestone: --- → M20
Hmmm. I don't know anything about that (it evolved a long, long, time ago).
I'll add this to my collection but I'm not sure that doing something about this
is a top priority).
About half of the code referenced in the test file seems needed. I can attach
my altered version later. I think it is probably safe to split the two trees
even though we end up with some code duplication.
Setting target milestone.
Target Milestone: --- → mozilla1.1
Is this bug still an issue (just going through verifyme bugs...)? I've
successfully built a number of times using --disable-tests in my .mozconfig and
not encountered this error, most recently being 20030914. I'm sorry if I
misunderstand the bug, but this looks like it should become INVALID or WORKSFORME.
Comment 9•21 years ago
|
||
Release builds are built with --disable-tests, and yes, this issue is no longer
present.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•