Re: [PD] Continuous Integration for Externals

telepatico asistido por maquinas. From: Pd-list <pd-list-boun...@lists.iem.at> on behalf of Thomas Mayer <tho...@residuum.org> Sent: Thursday, December 1, 2016 12:15 AM To: pd-list@lists.iem.at Subject: Re: [PD] Continuous Integration for Externals O

Re: [PD] Continuous Integration for Externals

On 01.12.2016 00:57, Thomas Mayer wrote: > The packages are then uploaded to my owncloud instance and are available > from https://ssl-account.com/cloud.residuum.org/index.php/s/380C60JAabnO7jk OS X builds on Travis are pretty much behind since yesterday, so give it several hours time until these

Re: [PD] Continuous Integration for Externals

Hello, On 29.11.2016 22:33, katja wrote: > On Tue, Nov 29, 2016 at 12:07 PM, katja wrote: > > [...] >> >> From https://docs.travis-ci.com/user/customizing-the-build/, I >> understand that Travis CI is also a community build farm (but >> obviously bigger and more

Re: [PD] Continuous Integration for Externals

> It seems that with Gitlab CI you can configure 'runners' on your own hardware for the project(s) that use it, right? So you can install dependencies and don't need to start with a clean slate for every build? That has several pro's and cons as compared with Travis. More DIY, but still with a

Re: [PD] Continuous Integration for Externals

-list@lists.iem.at Subject: Re: [PD] Continuous Integration for Externals Hi, On 29.11.2016 09:58, IOhannes m zmoelnig wrote: > On 2016-11-29 02:54, Thomas Mayer wrote: >> Should I use gcc or clang for compilation on OS X? Or both? > > i'd use $(CC). > > i see little merit in

Re: [PD] Continuous Integration for Externals

I just updated my pd.build (https://github.com/pierreguillot/pd.build/) repository that facilitate the creation of projects with CMake. I tried to add scripts that also facilitate the use of travis and I improved the documentation. I'll try to do a version of these scripts for Appveyor too and to

Re: [PD] Continuous Integration for Externals

Hi, On 29.11.2016 09:58, IOhannes m zmoelnig wrote: > On 2016-11-29 02:54, Thomas Mayer wrote: >> Should I use gcc or clang for compilation on OS X? Or both? > > i'd use $(CC). > > i see little merit in using a compiler that is actively being > phased out in the ecosystem (that is: why would

Re: [PD] Continuous Integration for Externals

On Tue, Nov 29, 2016 at 12:07 PM, katja wrote: [...] > > From https://docs.travis-ci.com/user/customizing-the-build/, I > understand that Travis CI is also a community build farm (but > obviously bigger and more professional than we could organize in Pd > community): > >

Re: [PD] Continuous Integration for Externals

> It seems that with Gitlab CI you can configure 'runners' on your own hardware for the project(s) that use it, right? Yes.  I could install gitlab-runner on my rpi2, get the "token" from gitlab, and have it sit there waiting to build. In that case, however, I'd essentially be letting remote

Re: [PD] Continuous Integration for Externals

On Tue, Nov 29, 2016 at 5:17 PM, Jonathan Wilkes wrote: >> Many of us don't have 'all' platforms available at their home or work > > > place and we sorely miss the Pd-extended build farm with its nightly > test builds. It seems useful to share knowledge and experience about >

Re: [PD] Continuous Integration for Externals

> Many of us don't have 'all' platforms available at their home or work place and we sorely miss the Pd-extended build farm with its nightly test builds. It seems useful to share knowledge and experience about an existing infrastructure like Travis. One option is "Giblab CI" which comes with

Re: [PD] Continuous Integration for Externals

> On Nov 29, 2016, at 5:28 AM, pd-list-requ...@lists.iem.at wrote: > > Should I use gcc or clang for compilation on OS X? Or both? clang is fine and using “gcc” actually calls clang anyway. I wouldn’t bother with both. If you want to explicitly build with gcc, you’ll need to install gcc via

Re: [PD] Continuous Integration for Externals

Before PdCon16~ I didn't even know about Travis. When IOhannes explained that it is an online continuous integration tool, my naive idea was 'can we use this to build our Pd libraries on 'all' platforms and route the builds back to us?' Many of us don't have 'all' platforms available at their

Re: [PD] Continuous Integration for Externals

> Should I use gcc or clang for compilation on OS X? Or both? On my local machine, I use clang and on travis I use gcc (but you can use both). Here are two other examples if you want: https://github.com/pierreguillot/pd-dummy https://github.com/CICM/HoaLibrary-PD/tree/dev/refactory

Re: [PD] Continuous Integration for Externals

[:travis-ci propaganda:] On 2016-11-29 01:09, Dan Wilcox wrote: >> On Nov 29, 2016, at 12:46 AM, pd-list-requ...@lists.iem.at wrote: >> >> Obiously, I would like to set up a Mac build machine as well. What do I >> need to install on a clean system via command line? > Install the build system via:

Re: [PD] Continuous Integration for Externals

On 2016-11-29 02:54, Thomas Mayer wrote: > Should I use gcc or clang for compilation on OS X? Or both? i'd use $(CC). i see little merit in using a compiler that is actively being phased out in the ecosystem (that is: why would you want to use gcc on OSX these days?) however, some of my

Re: [PD] Continuous Integration for Externals

Hi, On 28.11.2016 22:34, Thomas Mayer wrote: > Obiously, I would like to set up a Mac build machine as well. What do I > need to install on a clean system via command line? Has anybody else > tried to do that before? Yes, it has been tried by IOhannes, and Dan and Antoine have helped with their

Re: [PD] Continuous Integration for Externals

> On Nov 29, 2016, at 12:46 AM, pd-list-requ...@lists.iem.at wrote: > > Obiously, I would like to set up a Mac build machine as well. What do I > need to install on a clean system via command line? Install the build system via: xcode-select —install You don’t need to download Xcode from the

Re: [PD] Continuous Integration for Externals

On 11/28/2016 10:34 PM, Thomas Mayer wrote: > Hello, > > after watching the talk and discussion from Katja about external > development, I have started setting up my extension PuREST JSON for CI > builds on travis-ci.org. > > Linux amd64 and cross compilation for Windows with MXE is working, I >

Re: [PD] Continuous Integration for Externals

Hi all, Some Pd projects are currently build on Travis. JamomaPuredata for example : https://travis-ci.org/jamoma/JamomaPureData/ and also Gem : https://travis-ci.org/umlaeute/Gem among others. Best Antoine -- do it yourself http://antoine.villeret.free.fr 2016-11-28 22:34 GMT+01:00 Thomas