[Varnish] #998: Separation of Varnish and vmod builds

Varnish varnish-bugs at varnish-cache.org
Wed Aug 31 01:30:45 CEST 2011

#998: Separation of Varnish and vmod builds
 Reporter:  anders  |       Owner:  tfheen
     Type:  task    |      Status:  new   
 Priority:  normal  |   Milestone:        
Component:  build   |     Version:  3.0.0 
 Severity:  normal  |    Keywords:        
 To make building of vmods work painless in source-based package systems,
 it should be possible to build without relying on the Varnish source:

 - Varnish and vmods come with separate autoconf configure scripts, they
 are meant to be built separately?

 - To be able to build a vmod at convenience, the complete Varnish source
 must be installed?

 I had a brief discussion with Kristian/Tollef about this on the chat, and
 they said it should not be necessary to need the (compiled source) when
 buildin a vmod like libvmod-header. Should it need the source at all
 except what follows from a normal Varnish install?

 In order to make it possible to build and install libvmod-header without
 VARNISHSRC dir, I had to:

 - install vmod.py

 - install lots of additional header files: vct.h vmod_abi.h vrt.h vqueue.h
 vsb.h libvarnish.h miniobj.h vas.h vav.h http_headers.h vcl_returns.h (in
 include dir) cache.h heritage.h steps.h common.h acct_fields.h locks.h (in
 bin/varnishd dir).

 - remove VARNISHSRC checks in configure.ac for libvmod-header and replace

 +AC_CHECK_HEADERS([varnish/varnishapi.h], , AC_MSG_ERROR([Could not find
 +AC_CHECK_PROGS(VARNISHTEST, varnishtest, [AC_MSG_ERROR([Could not find
 varnishtest binary])])

 - adjust various paths for header files and vmod.py.

 The configure script for Varnish should either have an option to add vmods
 outside the Varnish tree, or vmods should be possible to build without

Ticket URL: <http://www.varnish-cache.org/trac/ticket/998>
Varnish <http://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list