1 .\" Hey, Emacs! This is -*-nroff-*- you know...
3 .\" pkgdata.1: manual page for the pkgdata utility
5 .\" Copyright (C) 2016 and later: Unicode, Inc. and others.
6 .\" License & terms of use: http://www.unicode.org/copyright.html
7 .\" Copyright (C) 2000-2009 IBM, Inc. and others.
9 .\" Manual page by Yves Arrouye <yves@realnames.com>.
10 .\" Modified by Michael Ow <mow@us.ibm.com>.
12 .TH PKGDATA 1 "6 February 2009" "ICU MANPAGE" "ICU @VERSION@ Manual"
15 \- package data for use by ICU
19 .BR "\-h\fP, \fB\-?\fP, \fB\-\-help"
22 .BI "\-v\fP, \fB\-\-verbose"
25 .BR "\-c\fP, \fB\-\-copyright"
27 .BI "\-C\fP, \fB\-\-comment" " comment"
30 .BI "\-m\fP, \fB\-\-mode" " mode"
32 .BI "\-p\fP, \fB\-\-name" " name"
33 .BI "\-O\fP, \fB\-\-bldopt" " options"
35 .BI "\-e\fP, \fB\-\-entrypoint" " name"
38 .BI "\-r\fP, \fB\-\-revision" " version"
41 .BI "\-F\fP, \fB\-\-rebuild"
44 .BI "\-I\fP, \fB\-\-install"
47 .BI "\-s\fP, \fB\-\-sourcedir" " source"
50 .BI "\-d\fP, \fB\-\-destdir" " destination"
53 .BI "\-T\fP, \fB\-\-tempdir" " directory"
60 takes a set of data files and packages them for use by ICU or
61 applications that use ICU. The typical reason to package files using
63 is to make their distribution easier and their loading by ICU faster
64 and less consuming of limited system resources such as file
66 Packaged data also allow applications to be distributed with fewer
67 resource files, or even with none at all if they link against the
68 packaged data directly.
71 supports a few different methods of packaging data that serve
80 In this mode, the different data files are bundled together as an
81 architecture-dependent file that can later be memory mapped for use by
82 ICU. Data packaged using this mode will be looked up under the ICU
83 data directory. Such packaging is easy to use for applications resource
84 bundles, for example, as long as the application can install the
85 packaged file in the ICU data directory.
87 Another packaging mode is the
91 mode, where the data files are compiled into a shared library. ICU
92 used to be able to dynamically load these shared libraries, but as of
93 ICU 2.0, such support has been removed. This mode is still useful for
94 two main purposes: to build ICU itself, as the ICU data is packaged as
95 a shared library by default; and to build resource bundles that are
96 linked to the application that uses them. Such resource bundles can
97 then be placed anywhere where the system's dynamic linker will be
98 looking for shared libraries, instead of being forced to live inside
99 the ICU data directory.
103 packaging mode is similar to the shared library one except that it
104 produces a static library.
105 .\" Note that many platforms are not able to
106 .\" dynamically load symbols from static object files, so for this reason
107 .\" .BR udata_setAppData()
109 .\" to install this data. As a convenience, pkgdata will build a C source file
110 .\" and a header file. Given a data package named
111 .\" .IR name, in the output
112 .\" directory will be created
115 .\" .IR name .h with the single
117 .\" .BR "udata_install_\fcIname\fB(UErrorCode *err)" ,
122 .\" turned into a valid C identifier.
123 .\" The application need to call this function once. The error code returned
125 .\" .BR udata_setAppData() .
127 .\" Data pakackaged in a library, whether shared or static,
128 .\" Subsequently, the application can access this data by passing
131 .\" rgument to functions such as
132 .\" .BR Bures_open() .
138 mode which simply copies the data files instead of packaging
139 them as a single file or library. This mode is mainly intended to
140 provide support for building ICU before it is packaged as separate
141 small packages for distribution with operating systems such as Debian
142 GNU/Linux for example. Please refer to the packaging documentation in
143 the ICU source distribution for further information on the use of this
147 builds, packages, installs, or cleans the appropriate data based on the options given
148 without the need to call GNU
153 .BR "\-h\fP, \fB\-?\fP, \fB\-\-help"
154 Print help about usage and exit.
156 .BR "\-v\fP, \fB\-\-verbose"
157 Display extra informative messages during execution.
159 .BR "\-c\fP, \fB\-\-copyright"
160 Include a copyright notice in the binary data.
162 .BI "\-C\fP, \fB\-\-comment" " comment"
163 Includes the specified
165 in the resulting data instead of the ICU copyright notice.
167 .BI "\-m\fP, \fB\-\-mode" " mode"
172 The different modes and their meaning are explained in the
174 section above. The valid mode names are
184 .BI "\-O\fP, \fB\-\-bldopt" " options"
185 Specify options for the builder. The builder is used internally by
187 to generate the correct packaged file. Such options include, but are
188 not limited to, setting variables used by
190 during the build of the packaged file. Note: If
192 is available, then this option is not needed.
194 .BI "\-p\fP, \fB\-\-name" " name"
195 Set the packaged file name to
197 This name is also used as the default entry point name after having
198 been turned into a valid C identifier.
200 .BI "\-e\fP, \fB\-\-entrypoint" " name"
201 Set the data entry point (used for linking against the data in a
202 shared library form) to
204 The default entry point name is the name set by the
205 .BI "\-n\fP, \fB\-\-name"
208 .BI "\-r\fP, \fB\-\-revision" " version"
209 Enable versioning of the shared library produced in
213 mode. The version number has the format
214 .I major\fP.\fIminor\fP.\fIpatchlevel
215 and all parts except for
217 are optional. If only
219 is supplied then the version is
222 for versioning purposes.
224 .BI "\-F\fP, \fB\-\-rebuild"
225 Force the rebuilding of all data and their repackaging.
227 .BI "\-I\fP, \fB\-\-install"
228 Install the packaged file (or all the files in the
230 mode). If the variable
232 is set it will be used for installation.
234 .BI "\-s\fP, \fB\-\-sourcedir" " source"
235 Set the source directory to
237 The default source directory is the current directory.
239 .BI "\-d\fP, \fB\-\-destdir" " destination"
240 Set the destination directory to
242 The default destination directory is the current directory.
244 .BI "\-T\fP, \fB\-\-tempdir" " directory"
245 Set the directory used to generate temporary files to
247 The default temporary directory is the same as the destination
250 .BI "\-d\fP, \fB\-\-destdir"
259 Copyright (C) 2000-2009 IBM, Inc. and others.