-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathREADME-hacking
More file actions
82 lines (57 loc) · 2.9 KB
/
README-hacking
File metadata and controls
82 lines (57 loc) · 2.9 KB
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
-*- outline -*-
These notes intend to help people working on the checked-out sources.
These requirements do not apply when building from a distribution tarball.
* Requirements
We've opted to keep only the highest-level sources in the GIT repository.
This eases our maintenance burden, (fewer merges etc.), but imposes more
requirements on anyone wishing to build from the just-checked-out sources.
Note the requirements to build the released archive are much less and
are just the requirements of the standard ./configure && make procedure.
Specific development tools and versions will be checked for and listed by
the bootstrap script. See README-prereq for specific notes on obtaining
these prerequisite tools.
Valgrind <http://valgrind.org/> is also highly recommended, if
Valgrind supports your architecture. See also README-valgrind.
While building from a just-cloned source tree may require installing a
few prerequisites, later, a plain `git pull && make' should be sufficient.
* First GIT checkout
You can get a copy of the source repository like this:
$ git clone git://git.savannah.gnu.org/cssc.git
$ cd cssc
The next step is to get and check other files needed to build,
which are extracted from other source packages:
$ ./bootstrap
If /bin/sh on your system is not POSIX-compatible, then you may need
to run "bootsrap" with a POSIX shell (for example /usr/xpg4/bin/sh on
Solaris).
And there you are! Just
$ ./configure --quiet --enable-binary
$ make
$ make check
Enjoy!
* If it's not your first GIT checkout
We used to check the googletest subdirectory out from svn, but this
has now moved to git. Therefore you may need to delete any existing
googletest directory before running "bootstrap".
* Compiler Warnings
You can also enable additional compiler warnings if you prefer, like
this:
$ ./configure --quiet --enable-binary --enable-gcc-warnings
The --enable-gcc-warnings option is probably useful only with glibc.
If you configure with this option, and spot a problem, please be sure
to send the report to the bug reporting address of this package, and
not to that of gnulib, even if the problem seems to originate in a
gnulib-provided file.
-----
Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
2011, 2019, 2024 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.