Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Synchronet
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
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
Main
Synchronet
Commits
b07d7375
Commit
b07d7375
authored
19 years ago
by
deuce
Browse files
Options
Downloads
Patches
Plain Diff
Add a note regarding DEBUG vs. RELEASE builds. Remove all the "Note:" bits.
And just have numbered notes.
parent
5b855527
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
docs/sbbsunix.txt
+20
-14
20 additions, 14 deletions
docs/sbbsunix.txt
with
20 additions
and
14 deletions
docs/sbbsunix.txt
+
20
−
14
View file @
b07d7375
...
...
@@ -221,20 +221,26 @@ Note: Skip to step 8 if you are updating an existing Synchronet installation.
B. Build the main executable (and utilities):
# gmake
Note: If you're linking with /usr/lib/libmozjs.so, don't forget to add
"JSLIB=mozjs" to the gmake command-line
Note: If X is not installed in /usr/X11R6,
use "gmake X_PATH=/path/to/X"
Note: To debug compile/link command-line problems, adding "VERBOSE=1"
to the gmake command-line can be very helpful
Note: Warnings (if any) can be safely ignored
Note: The "current" code in the CVS repository is in a fairly constant
state of change. And often, one or more projects will not build
successfully on any given platform. This is a common occurance
and is expected in a fluid development project such as this one.
If you'd like a verifiably-buildable source code base, either
download one of the source code archives (e.g. sbbs_src.tgz) or
use a release label (tag) when checking out files from CVS.
NOTES:
1: If you're linking with /usr/lib/libmozjs.so, don't forget to add
"JSLIB=mozjs" to the gmake command-line
2: If X is not installed in /usr/X11R6,
use "gmake X_PATH=/path/to/X"
3: To debug compile/link command-line problems, adding "VERBOSE=1"
to the gmake command-line can be very helpful
4: Warnings (if any) can be safely ignored
5: The "current" code in the CVS repository is in a fairly constant
state of change. And often, one or more projects will not build
successfully on any given platform. This is a common occurance
and is expected in a fluid development project such as this one.
If you'd like a verifiably-buildable source code base, either
download one of the source code archives (e.g. sbbs_src.tgz) or
use a release label (tag) when checking out files from CVS.
6: By default, this will build DEBUG binaries which will be larger,
slower, and consume more resources than a RELEASE build. If you
wish a RELEASE build, add "RELEASE=1" to the gmake command-line.
This will make it more difficult to send us usefull error reports
though.
C. Change to the src/sbbs3/scfg directory:
# cd /sbbs/src/sbbs3/scfg
...
...
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