December 02, 2017 Re: LDC 1.6.0-beta1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | On Saturday, 2 December 2017 at 15:47:23 UTC, Jacob Carlborg wrote:
> On 2017-12-02 13:41, kinke wrote:
>
>> Nope, unfortunately still waiting for one of my compadres to create and upload the OSX package.
>
> Have you thought of automatically build and upload packages using Travis CI?
That would be a good idea. Also, I uploaded the OS X package just now. (Didn't realise it wasn't built yet…). —David
|
December 03, 2017 Re: LDC 1.6.0-beta1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | On 2017-12-03 00:08, David Nadlinger wrote: > That would be a good idea. Also, I uploaded the OS X package just now. (Didn't realise it wasn't built yet…). —David Here's the Travis CI script for one of my projects [1] that uploads to a GitHub release, both for Linux and macOS. [1] https://github.com/jacob-carlborg/remarkify/blob/master/.travis.yml -- /Jacob Carlborg |
December 03, 2017 Re: LDC 1.6.0-beta1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | On Saturday, 2 December 2017 at 23:08:50 UTC, David Nadlinger wrote: > On Saturday, 2 December 2017 at 15:47:23 UTC, Jacob Carlborg wrote: >> On 2017-12-02 13:41, kinke wrote: >> >>> Nope, unfortunately still waiting for one of my compadres to create and upload the OSX package. >> >> Have you thought of automatically build and upload packages using Travis CI? Working on that. It's not that simple though; we use a custom LLVM, which Travis doesn't manage to build alone in a dedicated job (only ~66% before timing out). Luckily, there's AppVeyor and CircleCI which manage. So I need to finish automating the LLVM release before automating the LDC release. > That would be a good idea. Also, I uploaded the OS X package just now. (Didn't realise it wasn't built yet…). —David Thx. |
December 03, 2017 Re: LDC 1.6.0-beta1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to kinke | On 2017-12-03 12:52, kinke wrote: > Working on that. It's not that simple though; we use a custom LLVM, which Travis doesn't manage to build alone in a dedicated job (only ~66% before timing out). Hmm, I would need to do that as well for DStep :(. That's disappointing. Would caching help [1]? I've also though about using Docker, which could contain a pre-built, perhaps that's more complicated. > Luckily, there's AppVeyor and CircleCI which manage. So I need to finish automating the LLVM release before automating the LDC release. I see. [1] https://docs.travis-ci.com/user/caching/ -- /Jacob Carlborg |
Copyright © 1999-2021 by the D Language Foundation