author | Alasdair Lumsden <alasdairrr@gmail.com> |
Mon, 15 Aug 2011 19:04:02 +0000 | |
branch | oi_151a |
changeset 569 | 660c4109f92b |
parent 2 | 1c00d793498a |
permissions | -rw-r--r-- |
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
1 |
README.opensolaris.g11n v2.0, Jul 3, 2007 |
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
2 |
|
0 | 3 |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
4 |
OPENSOLARIS.ORG NEVADA G11N WORKSPACE BUILD INSTRUCTIONS |
0 | 5 |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
6 |
This file contains the instructions for checking out and building the G11N |
0 | 7 |
workspace for OpenSolaris, where to file bug or RFE (Request For Enhancement) |
8 |
reports, and also how to contribute. |
|
9 |
||
10 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
11 |
|
0 | 12 |
G11N Workspace Build Instructions |
13 |
--------------------------------- |
|
14 |
||
15 |
1. Install a build machine with the latest version of Solaris Express from: |
|
16 |
||
17 |
http://www.sun.com/software/solaris/solaris-express/get.jsp |
|
18 |
||
19 |
Currently, the build machines must have Developer System Support or higher |
|
20 |
meta-cluster and all locales installed. It is recommended to have at least |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
21 |
1GB of swap space or memory combined for a proper build. |
0 | 22 |
|
23 |
After the build machine installation, about 3.2GB of free disk space is |
|
24 |
needed to keep the downloaded tarballs and also to build. |
|
25 |
||
26 |
2. Download an install image of Sun Studio 11 for OpenSolaris, SPARC or |
|
27 |
x86/x64 from: |
|
28 |
||
29 |
http://opensolaris.org/os/community/tools/sun_studio_tools/sun_studio_11_tools/ |
|
30 |
||
31 |
This must be installed into /opt/SUNWspro/, i.e. your cc compiler should be |
|
32 |
available as /opt/SUNWspro/bin/cc. |
|
33 |
||
34 |
3. Download the closed binary tarballs by following the link from the following |
|
35 |
web page: |
|
36 |
||
37 |
http://www.opensolaris.org/os/community/int_localization/sources/ |
|
38 |
||
39 |
The binary tarballs contain binary objects that may not be on your current |
|
40 |
system but are needed by the workspace to build, and use the naming |
|
41 |
convention 'g11n-{closed,GPL}-bins-<DATE>.<PLATFORM>.tar.bz2'. Make sure |
|
42 |
you take the correct ones for your architecture, for instance, download |
|
43 |
'g11n-closed-bins-20061220.sparc.tar.bz2' and |
|
44 |
'g11n-GPL-bins-20061220.sparc.tar.bz2' if you are working on a SPARC-based |
|
45 |
system and 'g11n-closed-bins-20061220.i386.tar.bz2' and |
|
46 |
g11n-GPL-bins-20061220.i386.tar.bz2' if you are working on an x86/x64-based |
|
47 |
system. The tarballs are also organized by date, where the date is in |
|
48 |
the format of YYYYMMDD. |
|
49 |
||
50 |
4. Unpack the binary tarballs at the root file system as root: |
|
51 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
52 |
$ su - |
0 | 53 |
# bzcat g11n-closed-bins-20061220.sparc.tar.bz2 | (cd / ; tar xvf -) |
54 |
# bzcat g11n-GPL-bins-20061220.sparc.tar.bz2 | (cd / ; tar xvf -) |
|
55 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
56 |
5. Check out the latest source codes from live repository |
0 | 57 |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
58 |
# cd /build |
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
59 |
# hg clone ssh://[email protected]/hg/nv-g11n/g11n |
0 | 60 |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
61 |
More details about G11N live repository can be found from: |
0 | 62 |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
63 |
http://www.opensolaris.org/os/project/nv-g11n/documents/repository/ |
0 | 64 |
|
65 |
6. Set an environment variable called 'SRC' to the full path of the g11n |
|
66 |
directory, i.e., if you extracted it into a /build directory then SRC |
|
67 |
should be /build/g11n. In ksh: |
|
68 |
||
69 |
# export SRC=/build/g11n |
|
70 |
||
71 |
7. Add the necessary paths to your $PATH variable such as '/usr/ccs/bin' for |
|
72 |
make and '/opt/SUNWspro/bin' for compilers. These should be near |
|
73 |
the beginning so that they are the first to be picked up. |
|
74 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
75 |
# export PATH=/opt/SUNWspro/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/bin |
0 | 76 |
|
77 |
8. Run 'make all' to build the workspace in its entirety. This will compile |
|
78 |
and generate binary files and create an empty directory tree in |
|
79 |
$SRC/proto/$arch/fileroot where $arch is your machine's architecture, |
|
80 |
i.e., sparc or i386: |
|
81 |
||
82 |
# make all 2>&1 | tee make.log |
|
83 |
||
84 |
The '2>&1 | tee make.log' will write all output from the make into |
|
85 |
a file called make.log. This isn't strictly necessary but is useful for |
|
86 |
debugging purposes later. |
|
87 |
||
88 |
9. Run 'make install' to populate this directory tree. This will copy all |
|
89 |
necessary files into $SRC/proto/$arch/fileroot in the locations that they |
|
90 |
would be installed on your system: |
|
91 |
||
92 |
# make install 2>&1 | tee install.log |
|
93 |
||
94 |
10. Run 'make links' to set up the necessary permissions and symbolic links in |
|
95 |
the proto directory. This changes the permissions and owners of the files |
|
96 |
to what they would be on the installed system, and also creates all |
|
97 |
necessary symbolic links between files: |
|
98 |
||
99 |
# make links 2>&1 | tee links.log |
|
100 |
||
101 |
11. To install the G11N files on your system, the workspace will create |
|
102 |
a set of binary tarballs in $SRC/dist/$arch which, if extracted from |
|
103 |
the root of your machine, will install all of the components to their |
|
104 |
correct locations. There are three options for this: |
|
105 |
||
106 |
- All components in one tarball. This will bundle everything into |
|
107 |
the one tarball, approx 62MB in size depending on the architecture. |
|
108 |
Build this by running 'make tarball'. |
|
109 |
||
110 |
- One tarball per locale. This creates a separate tarball for each locale, |
|
111 |
using the locale name as the tarball name, plus a common tarball for |
|
112 |
components that are common across all locales. Build this by running |
|
113 |
'make tarballs'. |
|
114 |
||
115 |
- One tarball for a specific locale. If you only want to install one locale, |
|
116 |
then you can run 'make <locale>' where <locale> is the name of the locale |
|
117 |
you want to create the tarball for, e.g., 'make de_DE' for German locales. |
|
118 |
If you just provide the "short" locale name without the codeset, |
|
119 |
the tarball will contain all of the codesets for that locale. |
|
120 |
||
121 |
12. After installation |
|
122 |
||
123 |
Run tools/update_fonts_cache.sh to update fonts.cache-1 files |
|
124 |
possibly outdated by installing font files. |
|
125 |
(Otherwise desktop login may fail.) |
|
126 |
||
127 |
# $SRC/tools/update_fonts_cache.sh |
|
128 |
updating /usr/openwin/lib/X11/fonts/TrueType/ttmap/fonts.cache-1... |
|
129 |
updating /usr/openwin/lib/X11/fonts/TrueType/fonts.cache-1... |
|
130 |
updating /usr/openwin/lib/locale/ar/X11/fonts/TrueType/fonts.cache-1... |
|
131 |
updating /usr/openwin/lib/locale/ko.UTF-8/X11/fonts/TrueType/fonts.cache-1... |
|
132 |
updating /usr/openwin/lib/locale/en_US.UTF-8/X11/fonts/misc/fonts.cache-1... |
|
133 |
updating /usr/openwin/lib/locale/ko/X11/fonts/TrueType/fonts.cache-1... |
|
134 |
# |
|
135 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
136 |
|
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
137 |
|
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
138 |
|
0 | 139 |
Bug/RFE Reports |
140 |
--------------- |
|
141 |
||
142 |
To report a bug or an RFE, use the following web interface: |
|
143 |
||
144 |
https://www.opensolaris.org/bug/report.jspa |
|
145 |
||
146 |
Available category values are library and utility and subcategory values are |
|
147 |
l10n-common, l10n-asia, l10n-europe, l10n-japan, and l10n-message. |
|
148 |
||
149 |
Alternatively you can also inform and discuss your issue or idea with |
|
150 |
other community members at i18n-discuss at opensolaris.org mailing list and |
|
151 |
other language mailing lists shown at the following: |
|
152 |
||
153 |
http://www.opensolaris.org/os/community/int_localization/discussions/ |
|
154 |
||
155 |
||
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
156 |
|
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
157 |
|
0 | 158 |
How to Contribute |
159 |
----------------- |
|
160 |
||
161 |
If you would like make contributions (source, idea, translation, and so on), |
|
162 |
sending an email to i18n-discuss at opensolaris.org mailing list and |
|
163 |
discuss about the contribution would be a good start. |
|
164 |
||
165 |
You can also follow the Development Process at OpenSolaris.org shown at |
|
166 |
the following: |
|
167 |
||
168 |
http://www.opensolaris.org/os/community/on/os_dev_process/ |
|
169 |
||
170 |
and start a project. |
|
171 |
||
172 |
If bug or RFE that you're thinking about to contribute are not big enough for |
|
173 |
a project and if you have code changes already more or less, you can also |
|
174 |
simply file a bug or RFE report and send an email to request-sponsor at |
|
175 |
opensolaris.org *and* i18n-discuss at opensolaris.org asking for a sponsor. |
|
176 |
There are many emails that you can reference before you send out |
|
177 |
a request from the following: |
|
178 |
||
179 |
http://www.opensolaris.org/jive/forum.jspa?forumID=27 |
|
180 |
||
181 |
Shortly after your email, there will be a sponsor contacting you and work |
|
182 |
together with you to integrate your contributions into G11N or any other |
|
183 |
consolidation/community's workspaces as needed. |
|
2
1c00d793498a
update README.opensolaris.g11n with live repository information
simford
parents:
0
diff
changeset
|
184 |