Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvmod-backend_dyn
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
libvmod-backend_dyn
Commits
bcc63ff8
Commit
bcc63ff8
authored
Jun 25, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add CONTRIBUTING.rst, and move (corrected) dev instructions into it.
parent
a53aaa86
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
30 additions
and
44 deletions
+30
-44
CONTRIBUTING.rst
CONTRIBUTING.rst
+30
-0
README.rst
README.rst
+0
-22
vmod.vcc
src/vmod.vcc
+0
-22
No files found.
CONTRIBUTING.rst
0 → 100644
View file @
bcc63ff8
CONTRIBUTING
============
To contribute code or documentation, submit a pull request at the
`source repository website
<https://code.uplex.de/uplex-varnish/libvmod-backend_dyn>`_.
If you have a problem or discover a bug, you can post an `issue
<https://code.uplex.de/uplex-varnish/libvmod-backend_dyn/issues>`_ at
the website. You can also write to <varnish-support@uplex.de>.
For developers
--------------
The build specifies C99 conformance, all compiler warnings turned on,
and all warnings considered errors (compiler options ``-std=c99
-Werror -Wall -Wextra``).
The VMOD has been tested with both the gcc and clang compilers, and
should always compile and test successfully with both of them.
By default, ``CFLAGS`` is set to ``-g -O2``, so that symbols are
included in the shared library, and optimization is at level
``O2``. To change or disable these options, set ``CFLAGS`` explicitly
before calling ``make`` (it may be set to the empty string).
For development/debugging cycles, the ``configure`` option
``--enable-debugging`` is recommended (off by default). This will turn
off optimizations and function inlining, so that a debugger will step
through the code as expected.
README.rst
View file @
bcc63ff8
...
...
@@ -322,28 +322,6 @@ INSTALLATION
See `INSTALL.rst <INSTALL.rst>`_ in the source repository.
For developers
--------------
As with Varnish, you can use these ``configure`` options for developer
builds:
* ``--enable-developer-warnings``
* Set stricter error and warning levels for compilation. The VMOD
MUST always build successfully with this option enabled.
* ``--enable-debugging-symbols``
* Make the VMOD's symbols available to debuggers, core dumps and so forth.
* ``--enable-stack-protector``
* Emit extra code to avoid buffer overflows
See ``configure --help`` for a full list of configuration options and
environment variables.
AUTHOR
======
...
...
src/vmod.vcc
View file @
bcc63ff8
...
...
@@ -279,28 +279,6 @@ INSTALLATION
See `INSTALL.rst <INSTALL.rst>`_ in the source repository.
For developers
--------------
As with Varnish, you can use these ``configure`` options for developer
builds:
* ``--enable-developer-warnings``
* Set stricter error and warning levels for compilation. The VMOD
MUST always build successfully with this option enabled.
* ``--enable-debugging-symbols``
* Make the VMOD's symbols available to debuggers, core dumps and so forth.
* ``--enable-stack-protector``
* Emit extra code to avoid buffer overflows
See ``configure --help`` for a full list of configuration options and
environment variables.
AUTHOR
======
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment