Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvmod-re
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
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-re
Commits
f3609889
Commit
f3609889
authored
Nov 21, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move the INSTALLATION section of the docs into a separate file.
parent
047ec9f0
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
56 additions
and
92 deletions
+56
-92
INSTALL.rst
INSTALL.rst
+48
-0
README.rst
README.rst
+6
-48
vmod_re.vcc
src/vmod_re.vcc
+2
-44
No files found.
INSTALL.rst
0 → 100644
View file @
f3609889
INSTALLATION
============
Building from source
~~~~~~~~~~~~~~~~~~~~
The VMOD is built on a system where an instance of Varnish is
installed, and the auto-tools will attempt to locate the Varnish
instance, and then pull in libraries and other support files from
there.
Quick start
-----------
This sequence should be enough in typical setups:
1. ``./autogen.sh`` (for git-installation)
2. ``./configure``
3. ``make``
4. ``make check`` (regression tests)
5. ``make install`` (may require root: sudo make install)
Alternative configs
-------------------
If you have installed Varnish to a non-standard directory, call
``autogen.sh`` and ``configure`` with ``PKG_CONFIG_PATH`` pointing to
the appropriate path. For example, when varnishd configure was called
with ``--prefix=$PREFIX``, use::
PKG_CONFIG_PATH=${PREFIX}/lib/pkgconfig
export PKG_CONFIG_PATH
For developers
--------------
As with Varnish, you can use these ``configure`` options for stricter
compiling:
* ``--enable-developer-warnings``
* ``--enable-extra-developer-warnings`` (for GCC 4)
* ``--enable-werror``
The VMOD must always build successfully with these options enabled.
Also as with Varnish, you can add ``--enable-debugging-symbols``, so
that the VMOD's symbols are available to debuggers, in core dumps and
so forth.
README.rst
View file @
f3609889
...
@@ -107,8 +107,8 @@ CONTENTS
...
@@ -107,8 +107,8 @@ CONTENTS
========
========
* regex(STRING)
* regex(STRING)
* BOOL match_dyn(
PRIV_TASK,
STRING, STRING)
* BOOL match_dyn(STRING, STRING)
* STRING backref_dyn(
PRIV_TASK,
INT, STRING)
* STRING backref_dyn(INT, STRING)
* STRING version()
* STRING version()
.. _obj_regex:
.. _obj_regex:
...
@@ -189,7 +189,7 @@ match_dyn
...
@@ -189,7 +189,7 @@ match_dyn
::
::
BOOL match_dyn(
PRIV_TASK,
STRING, STRING)
BOOL match_dyn(STRING, STRING)
Description
Description
Compiles the regular expression given in the first argument,
Compiles the regular expression given in the first argument,
...
@@ -211,7 +211,7 @@ backref_dyn
...
@@ -211,7 +211,7 @@ backref_dyn
::
::
STRING backref_dyn(
PRIV_TASK,
INT, STRING fallback="**BACKREF FUNCTION FAILED**")
STRING backref_dyn(INT, STRING fallback="**BACKREF FUNCTION FAILED**")
Description
Description
Similar to the ``backref`` method, this function extracts the
Similar to the ``backref`` method, this function extracts the
...
@@ -251,49 +251,7 @@ versions that are compatible with other versions of Varnish.
...
@@ -251,49 +251,7 @@ versions that are compatible with other versions of Varnish.
INSTALLATION
INSTALLATION
============
============
The VMOD is built on a system where an instance of Varnish is
See `INSTALL.rst <INSTALL.rst>`_ in the project source repository.
installed, and the auto-tools will attempt to locate the Varnish
instance, and then pull in libraries and other support files from
there.
Quick start
-----------
This sequence should be enough in typical setups:
1. ``./autogen.sh`` (for git-installation)
2. ``./configure``
3. ``make``
4. ``make check`` (regression tests)
5. ``make install`` (may require root: sudo make install)
Alternative configs
-------------------
If you have installed Varnish to a non-standard directory, call
``autogen.sh`` and ``configure`` with ``PKG_CONFIG_PATH`` pointing to
the appropriate path. For example, when varnishd configure was called
with ``--prefix=$PREFIX``, use
PKG_CONFIG_PATH=${PREFIX}/lib/pkgconfig
export PKG_CONFIG_PATH
For developers
--------------
As with Varnish, you can use these ``configure`` options for stricter
compiling:
* ``--enable-developer-warnings``
* ``--enable-extra-developer-warnings`` (for GCC 4)
* ``--enable-werror``
The VMOD must always build successfully with these options enabled.
Also as with Varnish, you can add ``--enable-debugging-symbols``, so
that the VMOD's symbols are available to debuggers, in core dumps and
so forth.
AUTHORS
AUTHORS
=======
=======
...
@@ -361,7 +319,7 @@ SEE ALSO
...
@@ -361,7 +319,7 @@ SEE ALSO
* varnishd(1)
* varnishd(1)
* vcl(7)
* vcl(7)
* pcre(3)
* pcre(3)
*
http://lassekarstensen.wordpress.com/2013/12/19/converting-a-varnish-3-0-vmod-to-4-0/
*
source repository: https://code.uplex.de/uplex-varnish/libvmod-re
COPYRIGHT
COPYRIGHT
=========
=========
...
...
src/vmod_re.vcc
View file @
f3609889
...
@@ -187,49 +187,7 @@ versions that are compatible with other versions of Varnish.
...
@@ -187,49 +187,7 @@ versions that are compatible with other versions of Varnish.
INSTALLATION
INSTALLATION
============
============
The VMOD is built on a system where an instance of Varnish is
See `INSTALL.rst <INSTALL.rst>`_ in the project source repository.
installed, and the auto-tools will attempt to locate the Varnish
instance, and then pull in libraries and other support files from
there.
Quick start
-----------
This sequence should be enough in typical setups:
1. ``./autogen.sh`` (for git-installation)
2. ``./configure``
3. ``make``
4. ``make check`` (regression tests)
5. ``make install`` (may require root: sudo make install)
Alternative configs
-------------------
If you have installed Varnish to a non-standard directory, call
``autogen.sh`` and ``configure`` with ``PKG_CONFIG_PATH`` pointing to
the appropriate path. For example, when varnishd configure was called
with ``--prefix=$PREFIX``, use
PKG_CONFIG_PATH=${PREFIX}/lib/pkgconfig
export PKG_CONFIG_PATH
For developers
--------------
As with Varnish, you can use these ``configure`` options for stricter
compiling:
* ``--enable-developer-warnings``
* ``--enable-extra-developer-warnings`` (for GCC 4)
* ``--enable-werror``
The VMOD must always build successfully with these options enabled.
Also as with Varnish, you can add ``--enable-debugging-symbols``, so
that the VMOD's symbols are available to debuggers, in core dumps and
so forth.
AUTHORS
AUTHORS
=======
=======
...
@@ -297,4 +255,4 @@ SEE ALSO
...
@@ -297,4 +255,4 @@ SEE ALSO
* varnishd(1)
* varnishd(1)
* vcl(7)
* vcl(7)
* pcre(3)
* pcre(3)
*
http://lassekarstensen.wordpress.com/2013/12/19/converting-a-varnish-3-0-vmod-to-4-0/
*
source repository: https://code.uplex.de/uplex-varnish/libvmod-re
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