intl/icu/source/data/icu4j-readme.txt

Sat, 03 Jan 2015 20:18:00 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Sat, 03 Jan 2015 20:18:00 +0100
branch
TOR_BUG_3246
changeset 7
129ffea94266
permissions
-rw-r--r--

Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.

michael@0 1 ********************************************************************************
michael@0 2 * Copyright (C) 2008-2012, International Business Machines Corporation *
michael@0 3 * and others. All Rights Reserved. *
michael@0 4 * *
michael@0 5 * 6/26/08 - Created by Brian Rower - heavy copying from ICU4J readme & others *
michael@0 6 * *
michael@0 7 ********************************************************************************
michael@0 8
michael@0 9 Procedures for building ICU4J data from ICU4C data:
michael@0 10
michael@0 11 *Setup*
michael@0 12
michael@0 13 In the following,
michael@0 14 $icu4c_root is the ICU4C root directory
michael@0 15 $icu4j_root is the ICU4J root directory
michael@0 16 $jdk_bin is the JDK bin directory (for the jar tool)
michael@0 17
michael@0 18 1. Download and build ICU4C. For more instructions on downloading and building
michael@0 19 ICU4C, see the ICU4C readme at:
michael@0 20 http://source.icu-project.org/repos/icu/icu/trunk/readme.html#HowToBuild
michael@0 21 (Windows: build as x86, Release otherwise you will have to set 'CFG' differently below.)
michael@0 22
michael@0 23 *NOTE* You should do a full rebuild after any data changes.
michael@0 24 1a. If you didn't download from Subversion, you will also need the "icu4c-*-data.zip" file. Unpack this file and replace the icu/source/data directory's contents with the contents of the data directory from the zip file.
michael@0 25
michael@0 26
michael@0 27 2. Step 2 depends on whether you are on a Windows or a Unix-type
michael@0 28 platform.
michael@0 29
michael@0 30 *Windows*
michael@0 31
michael@0 32 2a. On the command line, cd to $icu4c_root\source\data.
michael@0 33
michael@0 34 2b. On the command line,
michael@0 35 nmake -f makedata.mak ICUMAKE=$icu4c_root\source\data\ CFG=x86\Release JAR="$jdk_bin\jar" ICU4J_ROOT=$icu4j_root icu4j-data-install
michael@0 36
michael@0 37 Continue with step 3 below, in Java:
michael@0 38
michael@0 39
michael@0 40 *Linux*
michael@0 41
michael@0 42 $icu4c_build is the ICU4C root build directory,
michael@0 43 which is $icu4c_root/source in an in-source build.
michael@0 44 (in other words, $icu4c_build is where you ran runConfigureICU or configure)
michael@0 45
michael@0 46 2c. On the command line, cd to $icu4c_build/data
michael@0 47
michael@0 48 2d. Do
michael@0 49 make JAR=$jdk_bin/jar ICU4J_ROOT=$icu4j_root icu4j-data-install
michael@0 50
michael@0 51 (You can omit the JAR if it's just jar.)
michael@0 52
michael@0 53 Continue with step 3, in Java:
michael@0 54
michael@0 55 Step 2 on either platform will produce two files: icudata.jar and
michael@0 56 icutzdata.jar in $icu4j_root/main/shared/data.
michael@0 57
michael@0 58 *Java*
michael@0 59
michael@0 60 3. After the ICU4C-side steps above, build the main target of the
michael@0 61 ICU4J ant build to unpack the jar files with the following commands:
michael@0 62
michael@0 63 cd $icu4j_root
michael@0 64 ant main

mercurial