Tim Wunder wrote: > Parish wrote: > > Tim Wunder wrote: > > > >> Daily builds all come with specific build numbers, YYYYMMDD##, to > identify > >> the build being used. I've recently taken to compiling mozilla on > >> my linux system and notice the build # is all 0's. How does one > >> specify a build # when compiling? The answer is probably in the > >> docs somewhere, but I didn't find anything in my cursory perousal > >> of the various README's. > >> > > > > You need to set BUILD_OFFICIAL=1 > > > > in your enviroment. > > > > See http://groups.google.com/groups?hl=en&th=3e45e6da69cd7525&rnum=1 > > > > HTH > > > > Thanks, Parish. > According to what the link you gave: > <quote> > The value is stored in content/global/build.dtd in > bin/chrome/toolkit.jar. It's a one-line text file: > > <!ENTITY buildId.label "Build ID: 0000000000"> > </quote> > > It looks like I can make my own :-) >
Well you could do, but you would have to edit toolkit.jar every build unless you always want the same build number, which seems a bit pointless to me. At least setting BUILD_OFFICIAL generates a meaningful ID. BTW, that thread I pointed you to also mentions MOZ_OFFICIAL_BUILD; I don't know what the differrence is - I'll have to use them myself and find out. > Regards, > Tim > > -- Software is like sex, it's better when it's free - Linus Torvalds Anti-spam e-mail address, change _AT_, sorry for the inconvenience
