intl/icu/source/tools/icuinfo/icuplugins_windows_sample.txt

Wed, 31 Dec 2014 07:22:50 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 07:22:50 +0100
branch
TOR_BUG_3246
changeset 4
fc2d59ddac77
permissions
-rw-r--r--

Correct previous dual key logic pending first delivery installment.

michael@0 1 # Copyright (C) 2009-2010 IBM Corporation and Others. All Rights Reserved.
michael@0 2 #
michael@0 3 # This is a sample ICU Plugins control file for Windows.
michael@0 4 # It's also an example control file for any platform.
michael@0 5 #
michael@0 6 # This file can be copied to, for example, C:\SOMEDIRECTORY\icuplugins##.txt
michael@0 7 # where ## is the major and minor ICU versions (i.e. just 96 for version 9.6.3)
michael@0 8 # and C:\SOMEDIRECTORY is any directory.
michael@0 9 #
michael@0 10 # Then, set the variable ICU_PLUGINS to C:\SOMEDIRECTORY
michael@0 11 #
michael@0 12 # Then, ICU will load the test plugin from either the debug or non-debug
michael@0 13 # plugin DLL (depending on whether ICU is in debug or non-debug state).
michael@0 14 #
michael@0 15 # To see the results, run the command "icuinfo -v -L"
michael@0 16 #
michael@0 17 # The format of this file is pretty simple.
michael@0 18 # These lines are comments.
michael@0 19 #
michael@0 20 # Non-comment lines have two or three elements in them, and look like this:
michael@0 21 #
michael@0 22 # LIBRARYNAME ENTRYPOINT [ CONFIGURATION .. ]
michael@0 23 #
michael@0 24 # Tabs or spaces separate the three items.
michael@0 25 #
michael@0 26 # LIBRARYNAME is the name of a shared library, either a short name if it is on the PATH,
michael@0 27 # or a full pathname.
michael@0 28 #
michael@0 29 # ENTRYPOINT is the short (undecorated) symbol name of the plugin's entrypoint.
michael@0 30 # see unicode/icuplug.h for information.
michael@0 31 #
michael@0 32 # CONFIGURATION is the entire rest of the line. It's passed as-is to the plugin.
michael@0 33 #
michael@0 34 #
michael@0 35 # This sample file tries to load 'myPlugin'.
michael@0 36 # It is in the testplug project. (You will need to rebuild either the debug or release version of this DLL.)
michael@0 37 # The configuration string isn't used, but is just an example
michael@0 38
michael@0 39 ## A high level test plugin that does nothing.
michael@0 40 testplug.dll myPlugin hello=world
michael@0 41
michael@0 42 ## A "bad" plugin that is low level but performs a malloc.
michael@0 43 ## Sometimes this is desired, but, note that it may cause
michael@0 44 ## later plugins to fail to load.
michael@0 45 #testplug.dll myPluginBad hello=world
michael@0 46
michael@0 47 ## A "high-level" plugin that does nothing.
michael@0 48 ## It will be loaded after the low level plugins.
michael@0 49 #testplug.dll myPluginHigh
michael@0 50
michael@0 51 ## A "low-level" plugin that does nothing.
michael@0 52 ## It will be loaded before the high level plugins.
michael@0 53 #testplug.dll myPluginLow
michael@0 54
michael@0 55 ## A low level plugin that just prints a message when uprv_malloc and related functions are called
michael@0 56 ## Note, it cannot be unloaded.
michael@0 57 #testplug.dll debugMemoryPlugin

mercurial