On 1/23/06, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Hi all, > > make -f client.mk ...: Mozilla products are packaged to allow the > use of a configuration file which can be used to pass the > configuration settings to the configure command.
This is a bit of a mouthful, but seems OK. Why not drop the first "configuration" and just say "to allow use of a file" > make uses the > client.mk file to get initial configuration and setup parameters, > then depending on the target parameter (build or install), either > runs the configure script and compiles the package or installs > the package. I don't think client.mk is used to get the configuration, althougth the scripts are called from client.mk. The mozconfig files is sourced and parsed whether you use client.mk or just ./configure, make, ... To me, the essence of the client.mk file is focusing on it is simply a Makefile with special targets rather than some strange new building tool. I would suggest something like the following. "client.mk is a custom Makefile provided by Mozilla providing many targets. The build target runs the initial configuration and compilation of the package while the install target installs the package." Definitely optional, but maybe: "The checkout target will pull the source code from CVS. When run with no arguments, client.mk will run the checkout and build targets." Those are my thoughts, but I don't see a really clean explanation. I also don't see any official description in the Moz Docs. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
