[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

2477.0. "build install & message catalogs" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Aug 08 1996 16:06

Date Of Receipt: 	 8-AUG-1996 11:56:16.99
From: 	FLUME::"rw@unx.dec.com"
To: 	buildhelp@zk3.dec.com
CC: 	
Subj: 	build install & message catalogs

Is there a "build install" type command for message catalogs?
When I do a build, I see the message cat being built into
"obj/alpha/usr/lib/nls/msg/en_US.ISO8859-1"; does that suffice
to make sure the catalogs are being built?

/Bob

T.RTitleUserPersonal
Name
DateLines
2477.1Re: build install & message catalogsAOSG::FILTERAutomatic Posting Software - mail to flume::puckFri Aug 23 1996 19:0570
Date Of Receipt: 	12-AUG-1996 13:34:32.54
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: 	rw@unx.dec.com
CC: 	buildhelp@DEC:.zko.flume
Subj: 	Re:  build install & message catalogs

There's also an install phase which would be good to test.  Here
are instructions from our web 
http://nsa.zk3.dec.com/rengweb/
click: ODE & Build Help for UNIX Development 
click: Code Development and Testing 
click: Doing Builds 
        Testing a "build install" operation 

----------
Testing a "build install" operation 

                 

General 

Note that, while this description applies generally to most of the commands part of the OS build
tree, it also applies to the kernel, but you must be at the top of the src/kernel tree to do the
install. This does not apply to the X build. 

Within ODE-II, developers have access to the release areas referred to in the ODE-II Developers
User Guide. The release areas are used for both installations and updates. In the ODE-II
Developers User Guide, this release area is under the directory release. In the DEC OSF/1 project,
the release area is in the directory output. 

In the DEC OSF/1 release area, output, no machine/operating system-dependent directories are
currently used. 

Examples 

Below is an example, which can be run within any directory in the src tree of a sandbox, for
running a test of the install phase of a build, local to your private sandbox. Note that the TOSTAGE
variable must be a full path; dot-relative paths are not allowed here. 

    % workon -sb sandbox set
    % mkdir path_to_sandbox_dir/output
    % su root
    # cd to required directory in src tree of sandbox
    # build -rc ~username/.sandboxrc \
        'TOSTAGE=path_to_sandbox_dir/output' install_all

An alternative way to set this up is as follows, defining TOSTAGE in the environment: 

    % workon -sb sandbox set
    % setenv TOSTAGE target_path
        (where eg. target_path = path_to_sandbox_dir/output)
    % mkdir -p $TOSTAGE
    % su root
    # cd to required directory in src tree of sandbox
    # build -rc ~username/.sandboxrc install_all

Finally, another alternative way to set this up is as follows, setting root's /.sandboxrc file to be the
same as your own, via a link (this eliminates the need for the -rc argument): 

    % workon -sb sandbox set
    % setenv TOSTAGE target_path
        (where eg. target_path = path_to_sandbox_dir/output, or 
        or eg. target_path = /tmp/testing)
    % mkdir -p $TOSTAGE
    % su root
    # ln -s ~user/.sandboxrc /
    # cd to required directory in src tree of sandbox
    # build install_all