scuffed-code/icu4c/source/samples/ufortune
2018-03-02 03:20:22 +00:00
..
resources ICU-13581 Fixing Samples. Add casts to quiet warnings, remove legacy sample from "all" VS Solution which does not build out of the box with ICU, ufortune only builds on Win32, and fix minor spelling/typo. 2018-02-23 03:01:30 +00:00
fortunedefs.mk ICU-12761 Adds Unicode copyright notice. 2016-09-28 22:12:27 +00:00
Makefile ICU-12761 Adds Unicode copyright notice. 2016-09-28 22:12:27 +00:00
readme.txt ICU-12761 Adds Unicode copyright notice. 2016-09-28 22:12:27 +00:00
ufortune.c ICU-12764 icu4c utf-8 source files, update Copyright notices. 2017-01-20 00:20:31 +00:00
ufortune.sln ICU-13171 Fix issues with ICU4C Samples, and various issues with vcxproj files. 2018-02-20 10:03:29 +00:00
ufortune.vcxproj ICU-13586 No actual code changes. This change cleans up redundancies in the VS project files, and pulls in common or shared settings from a shared 'props' file. This means that you can now change one single file to target either VS2015 or VS2017, instead of needing to change many files. It also allows the VS project files to share common defines as well, meaning that if you need to target something other than Windows 7, you can make one change in one file, instead of needing to make hundreds. Also included in this change are improvements to the VS Solution files in order to properly denote the dependencies of the projects, which might be needed in the future for possible parallel project builds. 2018-03-02 03:20:22 +00:00
ufortune.vcxproj.filters ICU-11609 add svn:eol-style property to vcxproj files. 2015-04-17 21:25:48 +00:00

Copyright (C) 2016 and later: Unicode, Inc. and others.
License & terms of use: http://www.unicode.org/copyright.html#License

Copyright (c) 2002-2005, International Business Machines Corporation and others. All Rights Reserved.
ufortune: a sample program demonstrating the use of ICU resource files by an application.

This sample demonstrates
         Defining resources for use by an application
         Compiling and packaging them into a dll
         Referencing the resource-containing dll from application code
         Loading resource data using ICU's API
         
Files:
    ./ufortune.c                 source code for the sample
    ./ufortune.sln               Windows MSVC workspace.  Double-click this to get started.
    ./ufortune.vcproj            Windows MSVC project file.
    ./Makefile                   Makefile for Unixes.  Needs gmake.
    resources/root.txt           Default resources  (text for messages in English)
    resources/es.txt             Spanish language resources source file..
    resources/res-file-list.txt  List of resource source files to be built
    resources/Makefile           Makefile for compiling resources, for Unixes.
    

To Build ufortune on Windows
    1.  Install and build ICU
    2.  In MSVC, open the workspace file icu\samples\ufortune\ufortune.sln
    3.  Choose a Debug or Release build.
    4.  Build.
	
To Run on Windows
    1.  Start a command shell window
    2.  Add ICU's bin directory to the path, e.g.
            set PATH=c:\icu\bin;%PATH%
        (Use the path to where ever ICU is on your system.)
    3.  cd into the ufortune directory, e.g.
            cd c:\icu\source\samples\ufortune\debug
    4.  Run it
            ufortune
     

To Build on Unixes
    1.  Build ICU.  Specify an ICU install directory when running configure,
        using the --prefix option.  The steps to build ICU will look something
        like this:
           cd <icu directory>/source
           runConfigureICU <platform-name> --prefix <icu install directory> [other options]
           gmake all
           
    2.  Install ICU, 
           gmake install
           
    3.  Build the sample
           cd <icu directory>/source/samples/ufortune
           export ICU_PREFIX= <icu install directory>
           gmake
           
 To Run on Unixes
           cd <icu directory>/source/samples/ufortune
           
           gmake check
              or
           export LD_LIBRARY_PATH=<icu install directory>/lib:.:$LD_LIBRARY_PATH
           ufortune
           
           
 Note:  The name of the LD_LIBRARY_PATH variable is different on some systems.
        If in doubt, run the sample using "gmake check", and note the name of
        the variable that is used there.  LD_LIBRARY_PATH is the correct name
        for Linux and Solaris.