mirror of
https://github.com/cuberite/TCLAP.git
synced 2025-08-03 09:47:05 -04:00
updates
This commit is contained in:
parent
00b45f04cb
commit
45a09c0997
182
INSTALL
Normal file
182
INSTALL
Normal file
@ -0,0 +1,182 @@
|
||||
Basic Installation
|
||||
==================
|
||||
|
||||
These are generic installation instructions.
|
||||
|
||||
The `configure' shell script attempts to guess correct values for
|
||||
various system-dependent variables used during compilation. It uses
|
||||
those values to create a `Makefile' in each directory of the package.
|
||||
It may also create one or more `.h' files containing system-dependent
|
||||
definitions. Finally, it creates a shell script `config.status' that
|
||||
you can run in the future to recreate the current configuration, a file
|
||||
`config.cache' that saves the results of its tests to speed up
|
||||
reconfiguring, and a file `config.log' containing compiler output
|
||||
(useful mainly for debugging `configure').
|
||||
|
||||
If you need to do unusual things to compile the package, please try
|
||||
to figure out how `configure' could check whether to do them, and mail
|
||||
diffs or instructions to the address given in the `README' so they can
|
||||
be considered for the next release. If at some point `config.cache'
|
||||
contains results you don't want to keep, you may remove or edit it.
|
||||
|
||||
The file `configure.in' is used to create `configure' by a program
|
||||
called `autoconf'. You only need `configure.in' if you want to change
|
||||
it or regenerate `configure' using a newer version of `autoconf'.
|
||||
|
||||
The simplest way to compile this package is:
|
||||
|
||||
1. `cd' to the directory containing the package's source code and type
|
||||
`./configure' to configure the package for your system. If you're
|
||||
using `csh' on an old version of System V, you might need to type
|
||||
`sh ./configure' instead to prevent `csh' from trying to execute
|
||||
`configure' itself.
|
||||
|
||||
Running `configure' takes awhile. While running, it prints some
|
||||
messages telling which features it is checking for.
|
||||
|
||||
2. Type `make' to compile the package.
|
||||
|
||||
3. Optionally, type `make check' to run any self-tests that come with
|
||||
the package.
|
||||
|
||||
4. Type `make install' to install the programs and any data files and
|
||||
documentation.
|
||||
|
||||
5. You can remove the program binaries and object files from the
|
||||
source code directory by typing `make clean'. To also remove the
|
||||
files that `configure' created (so you can compile the package for
|
||||
a different kind of computer), type `make distclean'. There is
|
||||
also a `make maintainer-clean' target, but that is intended mainly
|
||||
for the package's developers. If you use it, you may have to get
|
||||
all sorts of other programs in order to regenerate files that came
|
||||
with the distribution.
|
||||
|
||||
Compilers and Options
|
||||
=====================
|
||||
|
||||
Some systems require unusual options for compilation or linking that
|
||||
the `configure' script does not know about. You can give `configure'
|
||||
initial values for variables by setting them in the environment. Using
|
||||
a Bourne-compatible shell, you can do that on the command line like
|
||||
this:
|
||||
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
||||
|
||||
Or on systems that have the `env' program, you can do it like this:
|
||||
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
||||
|
||||
Compiling For Multiple Architectures
|
||||
====================================
|
||||
|
||||
You can compile the package for more than one kind of computer at the
|
||||
same time, by placing the object files for each architecture in their
|
||||
own directory. To do this, you must use a version of `make' that
|
||||
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
||||
directory where you want the object files and executables to go and run
|
||||
the `configure' script. `configure' automatically checks for the
|
||||
source code in the directory that `configure' is in and in `..'.
|
||||
|
||||
If you have to use a `make' that does not supports the `VPATH'
|
||||
variable, you have to compile the package for one architecture at a time
|
||||
in the source code directory. After you have installed the package for
|
||||
one architecture, use `make distclean' before reconfiguring for another
|
||||
architecture.
|
||||
|
||||
Installation Names
|
||||
==================
|
||||
|
||||
By default, `make install' will install the package's files in
|
||||
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
||||
installation prefix other than `/usr/local' by giving `configure' the
|
||||
option `--prefix=PATH'.
|
||||
|
||||
You can specify separate installation prefixes for
|
||||
architecture-specific files and architecture-independent files. If you
|
||||
give `configure' the option `--exec-prefix=PATH', the package will use
|
||||
PATH as the prefix for installing programs and libraries.
|
||||
Documentation and other data files will still use the regular prefix.
|
||||
|
||||
In addition, if you use an unusual directory layout you can give
|
||||
options like `--bindir=PATH' to specify different values for particular
|
||||
kinds of files. Run `configure --help' for a list of the directories
|
||||
you can set and what kinds of files go in them.
|
||||
|
||||
If the package supports it, you can cause programs to be installed
|
||||
with an extra prefix or suffix on their names by giving `configure' the
|
||||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
||||
|
||||
Optional Features
|
||||
=================
|
||||
|
||||
Some packages pay attention to `--enable-FEATURE' options to
|
||||
`configure', where FEATURE indicates an optional part of the package.
|
||||
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
|
||||
is something like `gnu-as' or `x' (for the X Window System). The
|
||||
`README' should mention any `--enable-' and `--with-' options that the
|
||||
package recognizes.
|
||||
|
||||
For packages that use the X Window System, `configure' can usually
|
||||
find the X include and library files automatically, but if it doesn't,
|
||||
you can use the `configure' options `--x-includes=DIR' and
|
||||
`--x-libraries=DIR' to specify their locations.
|
||||
|
||||
Specifying the System Type
|
||||
==========================
|
||||
|
||||
There may be some features `configure' can not figure out
|
||||
automatically, but needs to determine by the type of host the package
|
||||
will run on. Usually `configure' can figure that out, but if it prints
|
||||
a message saying it can not guess the host type, give it the
|
||||
`--host=TYPE' option. TYPE can either be a short name for the system
|
||||
type, such as `sun4', or a canonical name with three fields:
|
||||
CPU-COMPANY-SYSTEM
|
||||
|
||||
See the file `config.sub' for the possible values of each field. If
|
||||
`config.sub' isn't included in this package, then this package doesn't
|
||||
need to know the host type.
|
||||
|
||||
If you are building compiler tools for cross-compiling, you can also
|
||||
use the `--target=TYPE' option to select the type of system they will
|
||||
produce code for and the `--build=TYPE' option to select the type of
|
||||
system on which you are compiling the package.
|
||||
|
||||
Sharing Defaults
|
||||
================
|
||||
|
||||
If you want to set default values for `configure' scripts to share,
|
||||
you can create a site shell script called `config.site' that gives
|
||||
default values for variables like `CC', `cache_file', and `prefix'.
|
||||
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
||||
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
||||
`CONFIG_SITE' environment variable to the location of the site script.
|
||||
A warning: not all `configure' scripts look for a site script.
|
||||
|
||||
Operation Controls
|
||||
==================
|
||||
|
||||
`configure' recognizes the following options to control how it
|
||||
operates.
|
||||
|
||||
`--cache-file=FILE'
|
||||
Use and save the results of the tests in FILE instead of
|
||||
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
|
||||
debugging `configure'.
|
||||
|
||||
`--help'
|
||||
Print a summary of the options to `configure', and exit.
|
||||
|
||||
`--quiet'
|
||||
`--silent'
|
||||
`-q'
|
||||
Do not print messages saying which checks are being made. To
|
||||
suppress all normal output, redirect it to `/dev/null' (any error
|
||||
messages will still be shown).
|
||||
|
||||
`--srcdir=DIR'
|
||||
Look for the package's source code in directory DIR. Usually
|
||||
`configure' can determine that directory automatically.
|
||||
|
||||
`--version'
|
||||
Print the version of Autoconf used to generate the `configure'
|
||||
script, and exit.
|
||||
|
||||
`configure' also accepts some other, not widely useful, options.
|
@ -70,7 +70,7 @@ am__include = @am__include@
|
||||
am__quote = @am__quote@
|
||||
install_sh = @install_sh@
|
||||
|
||||
SUBDIRS = src include examples docs
|
||||
SUBDIRS = src include examples docs tests
|
||||
subdir = .
|
||||
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
|
||||
mkinstalldirs = $(SHELL) $(top_srcdir)/config/mkinstalldirs
|
||||
|
@ -1,13 +1,17 @@
|
||||
|
||||
noinst_PROGRAMS = test1 test2
|
||||
noinst_PROGRAMS = test1 test2 test3
|
||||
|
||||
test1_SOURCES = test1.cpp
|
||||
|
||||
test2_SOURCES = test2.cpp
|
||||
|
||||
test3_SOURCES = test3.cpp
|
||||
|
||||
test1_LDADD = $(top_builddir)/src/libtclap.a
|
||||
|
||||
test2_LDADD = $(top_builddir)/src/libtclap.a
|
||||
|
||||
test3_LDADD = $(top_builddir)/src/libtclap.a
|
||||
|
||||
INCLUDES = -I$(top_builddir)/include
|
||||
|
||||
|
@ -13,7 +13,7 @@ int main(int argc, char** argv)
|
||||
CmdLine cmd(argv[0], "Command description message", "0.9");
|
||||
|
||||
// Define a value argument and add it to the command line.
|
||||
ValueArg<string> nameArg("n","name","Name to print",true,"homer");
|
||||
ValueArg<string> nameArg("n","name","Name to print",true,"homer","string");
|
||||
cmd.add( nameArg );
|
||||
|
||||
// Define a switch and add it to the command line.
|
||||
|
@ -8,7 +8,9 @@ using namespace TCLAP;
|
||||
|
||||
int _intTest;
|
||||
float _floatTest;
|
||||
bool _boolTest;
|
||||
bool _boolTestA;
|
||||
bool _boolTestB;
|
||||
bool _boolTestC;
|
||||
string _stringTest;
|
||||
string _utest;
|
||||
|
||||
@ -23,7 +25,9 @@ int main(int argc, char** argv)
|
||||
<< "for int we got : " << _intTest<< endl
|
||||
<< "for string we got : " << _stringTest<< endl
|
||||
<< "for ulabeled we got : " << _utest << endl
|
||||
<< "for bool we got : " << _boolTest << endl;
|
||||
<< "for bool A we got : " << _boolTestA << endl
|
||||
<< "for bool B we got : " << _boolTestB << endl
|
||||
<< "for bool C we got : " << _boolTestC << endl;
|
||||
|
||||
}
|
||||
|
||||
@ -38,22 +42,30 @@ void parseOptions(int argc, char** argv)
|
||||
// Define arguments
|
||||
//
|
||||
|
||||
SwitchArg btest("B","existTest", "exist Test", false);
|
||||
SwitchArg btest("B","existTestB", "tests for the existence of B", false);
|
||||
cmd.add( btest );
|
||||
|
||||
ValueArg<string> stest("s", "stringTest", "string test", true, "homer");
|
||||
SwitchArg ctest("C","existTestC", "tests for the existence of C", false);
|
||||
cmd.add( ctest );
|
||||
|
||||
SwitchArg atest("A","existTestA", "tests for the existence of A", false);
|
||||
cmd.add( atest );
|
||||
|
||||
ValueArg<string> stest("s","stringTest","string test",true,"homer",
|
||||
"string");
|
||||
cmd.add( stest );
|
||||
|
||||
ValueArg<int> itest("i", "intTest", "integer test", true, 5);
|
||||
ValueArg<int> itest("i", "intTest", "integer test", true, 5, "int");
|
||||
cmd.add( itest );
|
||||
|
||||
ValueArg<double> ftest("f", "floatTest", "float test", false, 3.7);
|
||||
ValueArg<double> ftest("f", "floatTest", "float test", false, 3.7, "float");
|
||||
cmd.add( ftest );
|
||||
|
||||
ValueArg<string> utest("unTest","unlabeld test", "default");
|
||||
UnlabeledValueArg<string> utest("unTest","unlabeld test",
|
||||
"default","string");
|
||||
cmd.add( utest );
|
||||
|
||||
MultiArg<string> mtest("file names");
|
||||
UnlabeledMultiArg<string> mtest("fileName", "file names", "string");
|
||||
cmd.add( mtest );
|
||||
|
||||
//
|
||||
@ -61,15 +73,15 @@ void parseOptions(int argc, char** argv)
|
||||
//
|
||||
cmd.parse(argc,argv);
|
||||
|
||||
|
||||
|
||||
//
|
||||
// Set variables
|
||||
//
|
||||
_intTest = itest.getValue();
|
||||
_floatTest = ftest.getValue();
|
||||
_stringTest = stest.getValue();
|
||||
_boolTest = btest.getValue();
|
||||
_boolTestB = btest.getValue();
|
||||
_boolTestC = ctest.getValue();
|
||||
_boolTestA = atest.getValue();
|
||||
_utest = utest.getValue();
|
||||
|
||||
vector<string> v = mtest.getValue();
|
||||
|
89
examples/test3.cpp
Normal file
89
examples/test3.cpp
Normal file
@ -0,0 +1,89 @@
|
||||
|
||||
|
||||
#include <tclap/CmdLine.h>
|
||||
#include <iostream>
|
||||
#include <string>
|
||||
|
||||
using namespace TCLAP;
|
||||
|
||||
int _intTest;
|
||||
float _floatTest;
|
||||
bool _boolTestA;
|
||||
bool _boolTestB;
|
||||
bool _boolTestC;
|
||||
string _stringTest;
|
||||
string _utest;
|
||||
|
||||
void parseOptions(int argc, char** argv);
|
||||
|
||||
int main(int argc, char** argv)
|
||||
{
|
||||
|
||||
parseOptions(argc,argv);
|
||||
|
||||
cout << "for float we got : " << _floatTest << endl
|
||||
<< "for int we got : " << _intTest<< endl
|
||||
<< "for string we got : " << _stringTest<< endl
|
||||
<< "for ulabeled we got : " << _utest << endl
|
||||
<< "for bool A we got : " << _boolTestA << endl
|
||||
<< "for bool B we got : " << _boolTestB << endl
|
||||
<< "for bool C we got : " << _boolTestC << endl;
|
||||
|
||||
}
|
||||
|
||||
|
||||
void parseOptions(int argc, char** argv)
|
||||
{
|
||||
try {
|
||||
|
||||
CmdLine cmd(argv[0], "this is a message", "0.99" );
|
||||
|
||||
//
|
||||
// Define arguments
|
||||
//
|
||||
|
||||
SwitchArg btest("B","existTest B", "exist Test B", false);
|
||||
cmd.add( btest );
|
||||
|
||||
ValueArg<string> stest("s", "stringTest", "string test", true, "homer",
|
||||
"string");
|
||||
cmd.add( stest );
|
||||
|
||||
UnlabeledValueArg<string> utest("unTest","unlabeld test",
|
||||
"default","string");
|
||||
cmd.add( utest );
|
||||
|
||||
MultiArg<int> itest("i", "intTest", "multi int test", false,"int" );
|
||||
cmd.add( itest );
|
||||
|
||||
UnlabeledMultiArg<string> mtest("fileName","file names","fileNameString");
|
||||
cmd.add( mtest );
|
||||
|
||||
//
|
||||
// Parse the command line.
|
||||
//
|
||||
cmd.parse(argc,argv);
|
||||
|
||||
|
||||
|
||||
//
|
||||
// Set variables
|
||||
//
|
||||
_stringTest = stest.getValue();
|
||||
_boolTestB = btest.getValue();
|
||||
_utest = utest.getValue();
|
||||
|
||||
vector<int> vi = itest.getValue();
|
||||
for ( int i = 0; i < vi.size(); i++ )
|
||||
cout << "[-i] " << i << " " << vi[i] << endl;
|
||||
|
||||
vector<string> v = mtest.getValue();
|
||||
for ( int i = 0; i < v.size(); i++ )
|
||||
cout << "[ ] " << i << " " << v[i] << endl;
|
||||
|
||||
} catch ( ArgException e )
|
||||
{ cout << "ERROR: " << e.error() << " " << e.argId() << endl; }
|
||||
}
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user