-
Notifications
You must be signed in to change notification settings - Fork 2
/
README
116 lines (81 loc) · 3.18 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
A C++ Command line option parsing library
=========================================
Please refer to the automatically generated HTML documentation.
Thanks:
-------
Chris Haidinyak <chrish@techspecs.com> for reporting bugs on
error handling.
Debian:
-------
I use Debian GNU/Linux 3.0 for most of what I do.
To make a debian package, simply do `debuild'.
The HTML documentation is installed in the liboptionmm-dev
Debian package.
Red Hat:
--------
There's no support for making Red Hat packages just yet -
sorry. However, I do plan to make it at some point.
IDE's:
------
The sub-directory `ide' contains some project files for
various IDEs (Integrated Development Platforms).
`optionmm.dsw'
`liboptionmm.dsp'
`demo.dsp'
`tryit.dsp'
Microsoft Visual C++ 6.0 project and workspace files.
Note, that I use `.cc' as the extension for C++
implementation files, and `.hh' as the extension for
C++ declaration files. MSVC and Microsoft Visual
Studio (MSVS) does not understand those extension as
C++ files, so you need to do a bit of Registry magic
to get it to work. Here's how (also refer to the
documentation of MSVC and MSVS):
* Start `regedit'
* In the group `HKEY_CLASS_ROOT', add two new keys, by
selecting `New -> Key' from the pop-up menu (right
click), called `.cc' with value `cppfile' and
another called `.hh' with value `hppfile'.
* In the group `HKEY_CURRENT_USER', find the group for
MS Developer studio:
Software\Microsoft\DevStudio\<version>
There, you need to find the sub-entry for the
platform, typically something like:
Build System\Components\Platforms\Win32 (<cpu>)
In that group, there's another subgroup for the compiler:
Tools\C/C++ Compiler for <cpu>
Whew! OK. In this group, edit the `Input_Spec'
entry to contain `*.cc'.
* Going back to the Developer Studio group, find the
group for the editor, and it's language settings for
C/C++:
Text Editor\Tabs/Language Settings\C/C++
There's an entry called `FileExtensions' - edit that
qto contain `hh' and `cc'.
Once all that's done, you'll have nice syntax
highlighting and so on in MSVS when you open the
`optionmm' workspace.
`liboptionmm.dev'
`demo.dev'
`tryit.dev'
Dev-C++ project files.
MS Visual C++ 6.0:
------------------
To build using Microsoft Visual C++ 6.0 (MSVC), you should run
configure as follows:
./configure CC=`pwd`/ide/cl \
CXX=`pwd`/ide/cl \
CXXFLAGS="-GX" \
LD=link
--enable-dependency-tracking
The script "`pwd`/ide/cl" is a small wrapper around MSVC's
compiler "cl.exe" that simply prefixes all ".cc" files with
the option "/Tp" to force C++ compilation.
The flag "-GX" is to enable exception handling.
The option "--enable-dependency-tracking" is to have Autotools
track the dependencies of the source code.
Note, that `make check' report failure, but as is evident from
the output, the tests don't really fail. Hence, please don't
report that as a bug to me.
Christian Holm Christensen
<cholm@nbi.dk>