Lines Matching full:build
42 <a href="#HowToBuild">How To Build And Install ICU</a>
136 <p>This document describes how to build and install ICU on your machine. For
272 <p>The --enable-64bit-libs and --disable-64bit-libs options are now deprecated. By default, ICU will build binaries using the compiler's default setting. To request 32 or 64 bit libraries, use --with-library-bits=32 or --with-library-bits=64. For the old behavior, of attempting 64 bit libraries if possible, use --with-library-bits=64else32. Intltest now reports the bit width that ICU is currently running under.</p>
418 compiled into binary form during the ICU build process. It contains
420 function. Note that the build process must be run again after any
431 several of the following directories. This is to simplify the build
472 <li><b>out/build/</b> This directory contains intermediate (compiled)
476 <p>If you are creating a special ICU build, you can set the ICU_DATA
477 environment variable to the out/ or the out/build/ directories, but
489 the test suite, see the build instructions specific to your platform
497 about running the test suite, see the build instructions specific to your
505 information about running the test suite, see the build instructions
513 the subdirectories <b>out/build/</b> which is used for intermediate
521 invoking <i><ICU></i>/source/data/build/makedata.bat on Win32 or
542 ICU build for various release platforms.</td>
548 <td>Contains helper makefiles for platform specific build commands. Used
556 build all of ICU under one MSVC project.</td>
581 <h2><a name="HowToBuild" href="#HowToBuild" id="HowToBuild">How To Build And
876 "HowToBuildWindows">How To Build And Install On Windows</a></h3>
886 of Microsoft Visual C++ and other compilers are used to build ICU.</li>
905 build from the command line instead.</li>
910 <li>Choose the "Build" menu and select "Rebuild Solution". If you want to
911 build the Debug and Release at the same time, see the <a href=
937 Note:</strong></a> You can build ICU from the command line. Assuming that you
940 <i><ICU></i>\source\allinone\allinone.sln /build "Win32|Release"'. You can also
941 use Cygwin with this compiler to build ICU, and you can refer to the <a href=
942 "#HowToBuildCygwin">How To Build And Install On Windows with Cygwin</a>
948 not a 64 bit version of Windows, the build will fail. To set the active platform, two different possibilities are:</p>
951 <li>Choose "Build" menu, select "Configuration Manager...", and select
954 <li>Another way is to select the desired build configuration from "Solution
965 <li>Choose "Build" menu, select "Configuration Manager...", and select
968 <li>Another way is to select the desired build configuration from "Solution
974 Configuration Note:</strong></a> If you want to build the Win32 and x64 platforms and
975 Debug and Release configurations at the same time, choose "Build" menu, and select "Batch
976 Build...". Click the "Select All" button, and then click the "Rebuild"
980 "HowToBuildCygwin">How To Build And Install On Windows with Cygwin</a></h3>
1003 <p>There are two ways you can build ICU with Cygwin. You can build with gcc
1008 scripts still need Cygwin). To build with gcc, please follow the "<a href=
1009 "#HowToBuildUNIX">How To Build And Install On UNIX</a>" instructions, while
1010 you are inside a Cygwin bash shell. To build with Microsoft Visual C++,
1015 gcc build, which requires the Cygwin Bash command prompt. The Microsoft
1075 To Build And Install On UNIX</a></h3>
1089 build section</a> of this document for further details.</li>
1092 <p>Here are the steps to build ICU:</p>
1132 HP-UX multithreaded build issues</a> with newer compilers. Solaris users,
1134 multithreaded build issues</a>.</p>
1162 Build And Install On z/OS (OS/390)</a></h3>
1174 contain the location of this executable prior to build. Failure to add these
1175 tools to your PATH will cause ICU build failures or cause pkgdata to fail
1179 recommended that you build ICU on a local filesystem. Once ICU has been
1211 requires the PTF PQ69418 to build XPLINK enabled binaries.</li>
1222 Build And Install On UNIX</a> section.</li>
1229 addition, there is a z/OS specific environment variable (OS390BATCH) to build
1237 the normal z/OS UNIX build. This means that the z/OS UNIX (HFS) DLLs will
1307 "HowToBuildOS400">How To Build And Install On The IBM i Family (IBM i, i5/OS OS/400)</a></h3>
1326 <p>The following describes how to setup and build ICU. For background
1327 information, you should look at the <a href="#HowToBuildUNIX">UNIX build
1342 Set up the following environment variables and job characteristics in your build process
1360 <li>Run <tt>'gmake'</tt> to build ICU.</li>
1362 <li>Run <tt>'gmake check QIBM_MULTI_THREADED=Y'</tt> to build and run the tests.
1371 <p>This section will explain how to build ICU on one platform, but to produce binaries intended to run on another. This is commonly known as a cross compile.</p>
1372 <p>Normally, in the course of a build, ICU needs to run the tools that it builds in order to generate and package data and test-data.In a cross compilation setting, ICU is built on a different system from that which it eventually runs on. An example might be, if you are building for a small/headless system (such as an embedded device), or a system where you can't easily run the ICU command line tools (any non-UNIX-like system).</p>
1373 <p>To reduce confusion, we will here refer to the "A" and the "B" system.System "A" is the actual system we will be running on- the only requirements on it is are it is able to build ICU from the command line targetting itself (with configure or runConfigureICU), and secondly, that it also contain the correct toolchain for compiling and linking for the resultant platform, referred to as the "B" system.</p>
1374 <p>The autoconf docs use the term "build" for A, and "host" for B. More details at: <a href="http://www.gnu.org/software/autoconf/manual/html_node/Specifying-Names.html#Specifying-Names">http://www.gnu.org/software/autoconf/manual/html_node/Specifying-Names.html</a></p>
1390 <li>Build ICU in /buildA normally (using runConfigureICU or configure):
1397 <li>Build ICU in /buildB<br>
1398 <div class="note"><b>Note:</b> "<code>--with-cross-build</code>" takes an absolute path.</div>
1400 sh /icu/source/configure --host=<strong>i586-pc-haiku</strong> --with-cross-build=<strong>/buildA</strong>
1407 <!-- end build environment -->
1419 "#HowToBuildUNIX">UNIX build instructions</a>). When ICU is built on Windows,
1651 understand a few of the following build details.</p>
1655 <p>As delivered, the International Components for Unicode build as several
1658 executables you build will not be able to access International Components for
1701 directory, as the older libraries will used during the build, instead of the
1702 new ones, likely leading to an incorrectly build ICU. This is the proper
1711 <p>If you are using ICU's Makefiles to build ICU on a new platform, there are
1721 <p>For some people, it may not be necessary for completely build ICU. Most of
1722 the makefiles and build targets are for tools that are used for building
1745 <p>Try to follow the build steps from the <a href="#HowToBuildUNIX">UNIX</a>
1746 build instructions. If the configure script fails, then you will need to
1768 <li>Build and test ICU on your platform. It is very important that you run
