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 still have an error with compiling the 32 bit x86 version (see http://stackoverflow.com/q/40824438/124983).
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?
After I have figured out the builds, I will write a summary on how to set it up correctly, and will try to build deken packages as well, and upload those to a test environment before actually releasing it.
If anyone wants to work with the current state of affairs:
The builds are setup with a file called .travis.yml, that contains the configuration variables and a list of build machines:
https://github.com/residuum/PuRestJson/blob/travis-ci/.travis.yml
I currently have two separate files for each environment, *_before_install.sh and *_script.sh, the former is used to set up the build environment and should in a way also function as documentation on how to set up your local machine, while *_script builds the files.
https://github.com/residuum/PuRestJson/tree/travis-ci/travis-build
I hope to be able to finish that this year and write some documentation about it as a Christmas / Chanukka gift to the community.
Thanks, Thomas
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 Mayer thomas@residuum.org:
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 still have an error with compiling the 32 bit x86 version (see http://stackoverflow.com/q/40824438/124983).
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?
After I have figured out the builds, I will write a summary on how to set it up correctly, and will try to build deken packages as well, and upload those to a test environment before actually releasing it.
If anyone wants to work with the current state of affairs:
The builds are setup with a file called .travis.yml, that contains the configuration variables and a list of build machines:
https://github.com/residuum/PuRestJson/blob/travis-ci/.travis.yml
I currently have two separate files for each environment, *_before_install.sh and *_script.sh, the former is used to set up the build environment and should in a way also function as documentation on how to set up your local machine, while *_script builds the files.
https://github.com/residuum/PuRestJson/tree/travis-ci/travis-build
I hope to be able to finish that this year and write some documentation about it as a Christmas / Chanukka gift to the community.
Thanks, Thomas -- "When one's home has a really excellent computer capable of reaching other computers anywhere in the Galaxy, one scarcely needs to budge." (Janov Pelorat in: Isaac Asimov - Foundation's Edge) http://www.residuum.org/
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
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 still have an error with compiling the 32 bit x86 version (see http://stackoverflow.com/q/40824438/124983).
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?
i'm using travis-ci (including OSX) to build
and a couple of others (including pd-iem which aggregates a number of externals, not all from iem; but this is complicated)
https://travis-ci.org/pure-data/pure-data https://travis-ci.org/umlaeute/Gem https://travis-ci.org/iem-projects/pd-iemguts https://travis-ci.org/umlaeute/pd-iemnet
(replace 'travis-ci.org' with 'github.com' for the actual repos, to see how they are setup)
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 mails as well.
My library uses the Makefile from pd-lib-builder, and OS X builds are fat binaries containing both 32 and 64 bit versions, let's see if brew install <package list> --universal will take care of it.
Should I use gcc or clang for compilation on OS X? Or both?
Thanks, Thomas
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 CI-builds use clang AND gcc on linux, mainly to check for as many build problems as possible (which is my main motivation for using CI - as opposed to produce distributable artifacts)
fgasmdr IOhannes
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 you want to use gcc on OSX these days?)
however, some of my CI-builds use clang AND gcc on linux, mainly to check for as many build problems as possible (which is my main motivation for using CI - as opposed to produce distributable artifacts)
Capturing build problems is also one of my motivations, but getting distributable artifacts is another one.
I would like to add real unit tests to the setup, but currently my python scripts for starting pd are not working consistently, and to be honest, I have no idea how to test the Windows builds on a Linux machine.
Thanks, Thomas
and to be honest, I have no idea how to test the Windows builds on a Linux machine.
Well probably https://www.virtualbox.org/ will do. Normally not to test audio latency but surely to test the rest.
You can host a win7 virtual machine (don`t set up an xp, is pretty old). I'm on Win8.1 and use 3 VM, Ubuntu, OSX and Win10.
Hope it helps. Lucarda.
Mensaje telepatico asistido por maquinas.
From: Pd-list pd-list-bounces@lists.iem.at on behalf of Thomas Mayer thomas@residuum.org Sent: Tuesday, November 29, 2016 9:50 PM To: pd-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 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 CI-builds use clang AND gcc on linux, mainly to check for as many build problems as possible (which is my main motivation for using CI - as opposed to produce distributable artifacts)
Capturing build problems is also one of my motivations, but getting distributable artifacts is another one.
I would like to add real unit tests to the setup, but currently my python scripts for starting pd are not working consistently, and to be honest, I have no idea how to test the Windows builds on a Linux machine.
Thanks, Thomas -- "In an era when everything can be surveiled, all we have left is politeness." (Major Napier in: Neal Stephenson: The Diamond Age) http://www.residuum.org/
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list