Changeset 1648

Show
Ignore:
Timestamp:
02/16/07 16:47:04
Author:
pvanhoof
Message:

Renaming and moving the demo ui

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/INSTALL

    r1 r1648  
    1 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software 
    2 Foundation, Inc. 
    3  
    4    This file is free documentation; the Free Software Foundation gives 
     1Installation Instructions 
     2************************* 
     3 
     4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free 
     5Software Foundation, Inc. 
     6 
     7This file is free documentation; the Free Software Foundation gives 
    58unlimited permission to copy, distribute and modify it. 
    69 
    …… 
    811================== 
    912 
    10    These are generic installation instructions. 
     13These are generic installation instructions. 
    1114 
    1215   The `configure' shell script attempts to guess correct values for 
    …… 
    6871===================== 
    6972 
    70    Some systems require unusual options for compilation or linking that 
    71 the `configure' script does not know about.  Run `./configure --help' 
    72 for details on some of the pertinent environment variables. 
     73Some systems require unusual options for compilation or linking that the 
     74`configure' script does not know about.  Run `./configure --help' for 
     75details on some of the pertinent environment variables. 
    7376 
    7477   You can give `configure' initial values for configuration parameters 
    …… 
    8386==================================== 
    8487 
    85    You can compile the package for more than one kind of computer at the 
     88You can compile the package for more than one kind of computer at the 
    8689same time, by placing the object files for each architecture in their 
    8790own directory.  To do this, you must use a version of `make' that 
    …… 
    100103================== 
    101104 
    102    By default, `make install' will install the package's files in 
    103 `/usr/local/bin', `/usr/local/man', etc.  You can specify an 
    104 installation prefix other than `/usr/local' by giving `configure' the 
    105 option `--prefix=PATH'. 
     105By default, `make install' installs the package's commands under 
     106`/usr/local/bin', include files under `/usr/local/include', etc.  You 
     107can specify an installation prefix other than `/usr/local' by giving 
     108`configure' the option `--prefix=PREFIX'. 
    106109 
    107110   You can specify separate installation prefixes for 
    108111architecture-specific files and architecture-independent files.  If you 
    109 give `configure' the option `--exec-prefix=PATH', the package will use 
    110 PATH as the prefix for installing programs and libraries. 
    111 Documentation and other data files will still use the regular prefix. 
     112pass the option `--exec-prefix=PREFIX' to `configure', the package uses 
     113PREFIX as the prefix for installing programs and libraries. 
     114Documentation and other data files still use the regular prefix. 
    112115 
    113116   In addition, if you use an unusual directory layout you can give 
    114 options like `--bindir=PATH' to specify different values for particular 
     117options like `--bindir=DIR' to specify different values for particular 
    115118kinds of files.  Run `configure --help' for a list of the directories 
    116119you can set and what kinds of files go in them. 
    …… 
    123126================= 
    124127 
    125    Some packages pay attention to `--enable-FEATURE' options to 
     128Some packages pay attention to `--enable-FEATURE' options to 
    126129`configure', where FEATURE indicates an optional part of the package. 
    127130They may also pay attention to `--with-PACKAGE' options, where PACKAGE 
    …… 
    138141========================== 
    139142 
    140    There may be some features `configure' cannot figure out 
    141 automatically, but needs to determine by the type of machine the package 
    142 will run on.  Usually, assuming the package is built to be run on the 
    143 _same_ architectures, `configure' can figure that out, but if it prints 
    144 a message saying it cannot guess the machine type, give it the 
     143There may be some features `configure' cannot figure out automatically, 
     144but needs to determine by the type of machine the package will run on. 
     145Usually, assuming the package is built to be run on the _same_ 
     146architectures, `configure' can figure that out, but if it prints a 
     147message saying it cannot guess the machine type, give it the 
    145148`--build=TYPE' option.  TYPE can either be a short name for the system 
    146149type, such as `sun4', or a canonical name which has the form: 
    …… 
    157160 
    158161   If you are _building_ compiler tools for cross-compiling, you should 
    159 use the `--target=TYPE' option to select the type of system they will 
     162use the option `--target=TYPE' to select the type of system they will 
    160163produce code for. 
    161164 
    …… 
    168171================ 
    169172 
    170    If you want to set default values for `configure' scripts to share, 
    171 you can create a site shell script called `config.site' that gives 
    172 default values for variables like `CC', `cache_file', and `prefix'. 
     173If you want to set default values for `configure' scripts to share, you 
     174can create a site shell script called `config.site' that gives default 
     175values for variables like `CC', `cache_file', and `prefix'. 
    173176`configure' looks for `PREFIX/share/config.site' if it exists, then 
    174177`PREFIX/etc/config.site' if it exists.  Or, you can set the 
    …… 
    179182================== 
    180183 
    181    Variables not defined in a site shell script can be set in the 
     184Variables not defined in a site shell script can be set in the 
    182185environment passed to `configure'.  However, some packages may run 
    183186configure again during the build, and the customized values of these 
    …… 
    187190     ./configure CC=/usr/local2/bin/gcc 
    188191 
    189 will cause the specified gcc to be used as the C compiler (unless it is 
    190 overridden in the site shell script). 
     192causes the specified `gcc' to be used as the C compiler (unless it is 
     193overridden in the site shell script).  Here is a another example: 
     194 
     195     /bin/bash ./configure CONFIG_SHELL=/bin/bash 
     196 
     197Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent 
     198configuration-related scripts to be executed by `/bin/bash'. 
    191199 
    192200`configure' Invocation 
    193201====================== 
    194202 
    195    `configure' recognizes the following options to control how it 
    196 operates. 
     203`configure' recognizes the following options to control how it operates. 
    197204 
    198205`--help' 

  • trunk/Makefile.am

    r1647 r1648  
    5151        libtinymailui-gtk \ 
    5252        libtinymail-camel \ 
    53         tinymail docs \ 
     53        docs \ 
    5454        libtinymail-test tests \ 
    5555        bindings po \ 

  • trunk/autogen.sh

    r1647 r1648  
    1010 
    1111(test -f $srcdir/configure.ac \ 
    12   && test -f $srcdir/tests/tinymail/tny-main.c) || { 
     12  && test -f $srcdir/libtinymail/tny-folder.c) || { 
    1313    echo -n "**Error**: Directory "\`$srcdir\'" does not look like the" 
    1414    echo " top-level $PKG_NAME directory" 

  • trunk/configure.ac

    r1647 r1648  
    397397libtinymail-test/Makefile 
    398398tests/Makefile 
    399 tests/tinymail/Makefile 
     399tests/c-demo/Makefile 
    400400tests/shared/Makefile 
    401401tests/python-demo/Makefile 

  • trunk/tests/Makefile.am

    r1647 r1648  
    22 
    33if BUILD_DEMOUI 
    4 SUBDIRS += tinymail  
     4SUBDIRS += c-demo 
    55endif 
    66