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
2e3bd475
Commit
2e3bd475
authored
Jun 25, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move the installation instructions into INSTALL.rst.
parent
177b149a
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
42 additions
and
54 deletions
+42
-54
INSTALL.rst
INSTALL.rst
+34
-0
README.rst
README.rst
+4
-27
vmod.vcc
src/vmod.vcc
+4
-27
No files found.
INSTALL.rst
0 → 100644
View file @
2e3bd475
INSTALLATION
============
The
VMOD
is
built
against
a
Varnish
installation
,
and
the
autotools
use
``
pkg
-
config
(
1
)``
to
locate
the
necessary
header
files
and
other
resources
.
This
sequence
will
install
the
VMOD
::
>
./
autogen
.
sh
#
for
builds
from
the
git
repo
>
./
configure
>
make
>
make
check
#
to
run
unit
tests
in
src
/
tests
/*.
vtc
>
sudo
make
install
The
configure
step
requires
code
from
the
Autoconf
Archive
collection
of
m4
macros
.
If
you
encounter
difficulties
in
the
``
configure
``
step
,
make
sure
that
you
have
the
archive
installed
(
typically
as
the
package
``
autoconf
-
archive
``
on
many
distributions
).
If
you
have
installed
Varnish
in
a
non
-
standard
directory
,
call
``
autogen
.
sh
``
and
``
configure
``
with
the
``
PKG_CONFIG_PATH
``
environment
variable
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
By
default
,
the
vmod
``
configure
``
script
installs
the
vmod
in
the
same
directory
as
Varnish
,
determined
via
``
pkg
-
config
(
1
)``.
The
vmod
installation
directory
can
be
overridden
by
passing
the
``
VMOD_DIR
``
variable
to
``
configure
``.
Other
files
such
as
the
man
-
page
are
installed
in
the
locations
determined
by
``
configure
``,
which
inherits
its
default
``--
prefix
``
setting
from
Varnish
.
README.rst
View file @
2e3bd475
...
...
@@ -320,33 +320,7 @@ This VMOD requires Varnish 4.1.0.
INSTALLATION
============
The VMOD is built against a Varnish installation, and the autotools
use ``pkg-config(1)`` to locate the necessary header files and other
resources. This sequence will install the VMOD::
> ./autogen.sh # for builds from the git repo
> ./configure
> make
> make check # to run unit tests in src/tests/*.vtc
> make distcheck # run check and prepare a distribution tarball
> sudo make install
If you have installed Varnish in a non-standard directory, call
``autogen.sh`` and ``configure`` with the ``PKG_CONFIG_PATH``
environment variable 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
By default, the vmod ``configure`` script installs the vmod in
the same directory as Varnish, determined via ``pkg-config(1)``. The
vmod installation directory can be overridden by passing the
``VMOD_DIR`` variable to ``configure``.
Other files such as this man-page are installed in the locations
determined by ``configure``, which inherits its default ``--prefix``
setting from Varnish.
See `INSTALL.rst <INSTALL.rst>`_ in the source repository.
For developers
--------------
...
...
@@ -413,6 +387,9 @@ SEE ALSO
* varnishd(1)
* vcl(7)
* `"Writing a Director" <https://www.varnish-cache.org/docs/4.1/reference/directors.html/>`_
* source repository: https://code.uplex.de/uplex-varnish/libvmod-backend_dyn
* developer contact: <varnish-support@uplex.de>, and at the source
repository site
COPYRIGHT
=========
...
...
src/vmod.vcc
View file @
2e3bd475
...
...
@@ -277,33 +277,7 @@ This VMOD requires Varnish 4.1.0.
INSTALLATION
============
The VMOD is built against a Varnish installation, and the autotools
use ``pkg-config(1)`` to locate the necessary header files and other
resources. This sequence will install the VMOD::
> ./autogen.sh # for builds from the git repo
> ./configure
> make
> make check # to run unit tests in src/tests/*.vtc
> make distcheck # run check and prepare a distribution tarball
> sudo make install
If you have installed Varnish in a non-standard directory, call
``autogen.sh`` and ``configure`` with the ``PKG_CONFIG_PATH``
environment variable 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
By default, the vmod ``configure`` script installs the vmod in
the same directory as Varnish, determined via ``pkg-config(1)``. The
vmod installation directory can be overridden by passing the
``VMOD_DIR`` variable to ``configure``.
Other files such as this man-page are installed in the locations
determined by ``configure``, which inherits its default ``--prefix``
setting from Varnish.
See `INSTALL.rst <INSTALL.rst>`_ in the source repository.
For developers
--------------
...
...
@@ -370,6 +344,9 @@ SEE ALSO
* varnishd(1)
* vcl(7)
* `"Writing a Director" <https://www.varnish-cache.org/docs/4.1/reference/directors.html/>`_
* source repository: https://code.uplex.de/uplex-varnish/libvmod-backend_dyn
* developer contact: <varnish-support@uplex.de>, and at the source
repository site
COPYRIGHT
=========
...
...
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