Re: svn commit: r1869697 - in /httpd/httpd/trunk: .travis.yml buildconf test/travis_run_linux.sh

[Joe Orton]

On Fri, Nov 15, 2019 at 08:10:28PM +0100, Ruediger Pluem wrote:
> > --- httpd/httpd/trunk/test/travis_run_linux.sh (original)
> > +++ httpd/httpd/trunk/test/travis_run_linux.sh Tue Nov 12 12:45:57 2019
> > @@ -1,7 +1,7 @@
> >  #!/bin/bash -ex
> >  ### Installed apr/apr-util don't include the *.m4 files but the
> >  ### Debian packages helpfully install them, so use the system APR to 
> > buildconf
> > -./buildconf --with-apr=/usr/bin/apr-1-config
> > +./buildconf --with-apr=/usr/bin/apr-1-config ${BUILDCONFIG}
> 
> Why don't we use the APR sources we download in travis_before_linux.sh at 
> least if APR_VERSION is set?
> Like
> 
> ./buildconf --with-apr=$HOME/build/apr-${APR_VERSION} ${BUILDCONFIG}

Mainly because of caching - the ~/build/apr-* directories are only 
created in the case where a cached ~/root/apr-* is not available.  It 
might be useful to try more complicated combinations of buildconf too, 
though this is simple and works everywhere for now.

Regards, Joe

Re: Help needed to test Windows builds in Travis

[William A Rowe Jr]

The  https://github.com/appsuite/oss-httpd-build/tree/master/mak tree
contains
all the tooling we've used to generate convenience binaries.
Makefile.build-win
should be what you are looking for; we no longer test .dsp/.mak based
builds,
only CMake logic. But testing both while they remain 'supported' is a very
wise
idea.



On Fri, Nov 8, 2019 at 12:56 AM Luca Toscano  wrote:

> Hi everybody,
>
> if you build httpd for Windows can you give us a list of commands and
> steps that you usually do? I am not familiar enough with the platform
> and [1] is still a bit cryptic to me :)
> The end goal is to add the build steps to our Travis config, to run
> them every time that a commit happens.
>
> Thanks in advance!
>
> Luca
>
> [1] https://httpd.apache.org/docs/2.4/platform/win_compiling.html
>