Re: [boost] Seeking help to build GitHub forks on AppVeyor and Travis

Subject: Re: [boost] Seeking help to build GitHub forks on AppVeyor and Travis
From: Cromwell Enage (cromwell.enage_at_[hidden])
Date: 2018-04-22 10:25:18

On Sun, Apr 22, 2018 at 3:57 AM, John Maddock via Boost <
boost_at_[hidden]> wrote:

> On 21/04/2018 21:19, Cromwell Enage via Boost wrote:
>
>> [snip]
>>
>> 2. On my Boost.Parameter fork, one of the AppVeyor jobs gets cut off after
>> 1 hour.  How do I split the job into several jobs, one for each compiler
>> or
>> smaller set of compilers?
>>
>
> One per compiler is easy - see https://github.com/boostorg/ty
> pe_traits/blob/develop/appveyor.yml for an example.
>

Okay, got that working.

> In extreme cases, that might not be enough of a split, in which case you
> can split the tests for each compiler into multiple chunks as well:
> https://github.com/boostorg/math/blob/develop/.travis.yml
>

I shouldn't need to do this, but I'll keep that in mind.

>
>> 3. The Boost.MultiArray project on GitHub doesn't have AppVeyor or Travis
>> configuration files, so I created a couple for my fork based on the ones
>> that exist in Boost.Parameter.  The AppVeyor jobs error out because they
>> don't recognize the compile-fail rule when running the Jamfile script.
>> Any
>> clues as to what I'm missing?
>>
>
> No, but make sure the Jamfile has
>
> import testing ;
>
> and that Boost.Build is installed.
>
>
>> 4. On my Boost.MultiArray fork, one of the Travis jobs builds fine, but
>> the
>> other fails because <boost/array.hpp> is not found.  Has anyone else run
>> into this issue?  If so, what was your workaround?
>>
>
> You have a dependency not installed, the
>
> - python tools/boostdep/depinst/depinst.py library_name
>
> line should take care of this - did you forget to update the library name
> in that part?
>

Yes, I did.  The tests work fine, now.

> HTH, John.
>

It did, thank you!
Cromwell D. Enage