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