204450 - problems if the top-level folder isnt called mozilla

Status: RESOLVED WONTFIX

(SeaMonkey :: Build Config, defect)

Description

[Jonathan Wilson]

basicly, if the top level folder (with client.mk, configure.in and stuff) isnt
called mozilla (so c:\mozilla is ok & c:\firebird\mozilla is ok but c:\firebird
isnt), the build system wont create .mozconfig.mk wont be created in the correct
place.
I dont know if there are other problems with not having the top level folder
called mozilla. I also cant find any documentation indicating it it has to be
called mozilla or not.

If there are reasons it needs to be called mozilla, this fact should be
documented in more places. If it doesnt need to be called mozilla, the
.mozconfig.mk issue and any others should be fixed.

Tested on Win32, dont know if/how it affects other platforms (MAC, Unix etc)

Comment 1

[Michiel van Leeuwen (email: mvl+moz@)]

When you checked out the source from cvs. It generated the mozilla dir. So that
directory is part of the tree.
Now you rename the dir. It can be expected that things like that will break
things. Why would renaming stuff just work?

Comment 2

[[e-mail]]

developers have so much better things to spend their time working on.

if you want to update the docs, submit a patch and reopen. it should be a one-liner.