Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
pike
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pikelang
pike
Commits
692ab38b
Commit
692ab38b
authored
22 years ago
by
Martin Stjernholm
Browse files
Options
Downloads
Patches
Plain Diff
Fixed some typos.
Rev: README-CVS:1.21
parent
408db9c0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README-CVS
+11
-11
11 additions, 11 deletions
README-CVS
with
11 additions
and
11 deletions
README-CVS
+
11
−
11
View file @
692ab38b
$Id: README-CVS,v 1.2
0
2003/0
2
/2
0
00:
10:52
mast Exp $
$Id: README-CVS,v 1.2
1
2003/0
3
/2
1
00:
25:21
mast Exp $
HOW TO BUILD PIKE FROM CVS
HOW TO BUILD PIKE FROM CVS
...
@@ -60,35 +60,35 @@ depend Build the files that tracks dependencies between
...
@@ -60,35 +60,35 @@ depend Build the files that tracks dependencies between
correct rebuilding if some of the source files
correct rebuilding if some of the source files
change, but not if you only intend to use the
change, but not if you only intend to use the
build tree once. It's not run by default.
build tree once. It's not run by default.
source Prepare the source tree for compil
i
ation without
source Prepare the source tree for compilation without
the need for a preexisting installed pike.
the need for a preexisting installed pike.
force_autoconfig Force
s
a build of the configure scripts. This is
force_autoconfig Force a build of the configure scripts. This is
useful e.g. if a new module directory is added in
useful e.g. if a new module directory is added in
the CVS.
the CVS.
force_configure Force
s
configure to be run (recursively). If
force_configure Force configure to be run (recursively). If
you've installed a new library and want pike to
you've installed a new library and want pike to
detect it, then the simplest way is to remove
detect it, then the simplest way is to remove
config.cache in the build directory (or perhaps
config.cache in the build directory (or perhaps
just delete the relevant variables in it) and then
just delete the relevant variables in it) and then
use this target.
use this target.
dump_modules Dump
s
the Pike modules directly in the build tree.
dump_modules Dump the Pike modules directly in the build tree.
That makes pike load faster if it's run directly
That makes pike load faster if it's run directly
from there, e.g. through the bin/pike script (see
from there, e.g. through the bin/pike script (see
below). These dumped modules are not used for
below). These dumped modules are not used for
anything else. After this has been run once, any
anything else. After this has been run once, any
changed Pike modules will be redumped
changed Pike modules will be redumped
automatically by the main build targets.
automatically by the main build targets.
undump_modules Remove
s
any modules dumped by dump_modules, and
undump_modules Remove any modules dumped by dump_modules, and
remove
s
the redump step described above.
remove the redump step described above.
force_dump_modules Force
s
all Pike modules to be redumped, not just
force_dump_modules Force all Pike modules to be redumped, not just
those whose source files have changed.
those whose source files have changed.
snapshot Create a snapshot export tarball.
snapshot Create a snapshot export tarball.
export Create a source dist and bump up the build number
export Create a source dist and bump up the build number
(if you have cvs write access). Please do not
(if you have cvs write access). Please do not
check in the generated files.
check in the generated files.
clean Remove
s
all the built binary files.
clean Remove all the built binary files.
cvsclean Remove
s
all files that are generated automatically,
cvsclean Remove all files that are generated automatically,
i.e. bring
s
the tree back to the state as if it
i.e. bring the tree back to the state as if it
was checked out from the CVS.
was checked out from the CVS.
If you want to pass arguments to the configure script (see below), the
If you want to pass arguments to the configure script (see below), the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment