Lines Matching full:libraries
97 Unicode (ICU) libraries provide robust and full-featured Unicode services on
98 a wide variety of platforms to help this design goal. The ICU libraries
271 Design</a> section of the User's Guide to see which libraries you need for
273 and the common (<code>[lib]icuuc</code>) libraries in order to use ICU.</p>
499 <td>Contains the import libraries for linking ICU into your Windows
506 <td>Contains the libraries and executables for using ICU on Windows.</td>
550 and statically linked ICU libraries become smaller.
600 <li><b>Static libraries:</b> It may make sense to build the ICU code
601 into static libraries (.a) rather than shared libraries (.so/.dll).
680 International Components for Unicode libraries, necessary ICU building
734 libraries and tools in <i><ICU></i>\bin\. The headers are in
735 <i><ICU></i>\include\ and the link libraries are in
815 or Microsoft Visual C++. If you use gcc, the resulting libraries and tools
817 resulting libraries and tools do not depend on Cygwin and can be more easily
846 <li>Type <tt>"make"</tt> to compile the libraries and all the data files.
890 defined in user code that links against ICU's static libraries.)</li>
931 your platform) to compile the libraries and all the data files. The proper
1050 <p>By default, ICU builds its libraries into the UNIX file system (HFS). In
1052 some libraries into the z/OS native file system. This is useful, for example,
1064 set that contains the dynamic link libraries (DLLs) and the LOADEXP
1233 products. Usually only the libraries need to be considered for packaging.</p>
1250 <li>The installation script should install the ICU libraries into the
1255 ICU distribution from conflicting with any libraries that you need. On
1261 gives a more complete description of the libraries.</p>
1264 "ICU has several libraries for you to use.">
1266 Here is an example of libraries that are frequently packaged.
1286 <td>Data required by the Common and I18n libraries. There are many ways
1299 <td>Base library required by all other ICU libraries.</td>
1357 <p>Normally only the above ICU libraries need to be considered for packaging.
1358 The versionless symbolic links to these libraries are only needed for easier
1433 ICU thread safe with RogueWave and other libraries using the 2.0 Standard C++
1479 Unicode libraries. Alternatively, you can copy the DLL files into a directory
1507 non-standard location, you may need to add the location of your ICU libraries
1510 variable for your system). The ICU libraries may not link or load properly
1515 instruct the linker to always look for the libraries where they are
1517 your own applications and libraries against ICU, too. Please refer to your
1521 directory, as the older libraries will used during the build, instead of the
1548 include platform dependent DLLs/shared/static libraries. For details see the
1560 you try to completely port and test ICU before using the libraries for your
