29597 - Cannot build Mozilla from read-only device

Status: RESOLVED WONTFIX

(SeaMonkey :: Build Config, defect, P3)

Description

[cls]

Currently, it's not possible to build Mozilla from a read-only device such as a
read-only nfs mount or a cdrom.  There are several instances where we modify
files in the source directory rather than the directory where Mozilla is being
built.  Under windows, I don't think it's even possible to build using a
separate drive than the source.  In the classic 4.x source, there was a MOZ_OUT
variable that could be set but it doesn't appear to be used anyomre.

Comment 1

[Chris Yeh]

I would be _really_ suprised if MOZ_OUT was even close to working. It's probably 
bitrotted to a point where you'd have to re-write it.

Comment 2

[Daniel Veditz [:dveditz]]

MOZ_OUT also only affected the final DIST export location, the .obj files from 
individual directories were still built in the same place they are now.

The main reason for MOZ_OUT was that the executable and .DLL's were buried way 
down in the tree and weren't in dist at all. They were in 
ns/cmd/windows/src/mkfiles32/win32_d.obj or something obscure like that.

Comment 3

[Chris Yeh]

mass re-assign of all bugs where i was listed as the qa contact

Comment 4

[cls]

I've checked in a patch for unix that handles the files that were being modified
in the source tree.  On the unix side, all we have left is the fact that tmp
.mozconfig.mk files are created in $(topsrcdir) if you use 'make -f client.mk
build'.

Comment 5

[hacker formerly known as [e-mail]]

I think that we're about as close as we're going to get.  Plus bug 141834 is
going to render this null and void on win32.