Re: [PD] Purr Data beta 2

Yeah, I ran that. I was thinking of the following for new users so the install itself is not sent and then the setting is permanent: export HOMEBREW_NO_ANALYTICS=1 && /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)” && brew analytics off

Re: [PD] Purr Data beta 2

> On Oct 14, 2016, at 11:37 AM, Jonathan Wilkes wrote: > > One snag-- any idea how to get plugin~ building using only Homebrew libs? I > need > ladspa.h but there's no package for it. I suppose I can just wget it if > nothing else… Should work fine as long as ladspa

Re: [PD] Purr Data beta 2

com> To: Jonathan Wilkes <jancs...@yahoo.com> Cc: Matt Barber <brbrof...@gmail.com>; Pd-List <pd-list@lists.iem.at> Sent: Wednesday, October 12, 2016 11:53 AM Subject: Re: [PD] Purr Data beta 2 On Oct 12, 2016, at 9:30 AM, Jonathan Wilkes <jancs...@yahoo.com> wrote:

Re: [PD] Purr Data beta 2

> On Oct 12, 2016, at 9:30 AM, Jonathan Wilkes wrote: > > When building the app bundle, Hans (I think) wrote a script that can grab the > /opt/local/lib dependencies, copy them to the app bundle, and revise the path > in the binary using @executable_path to make sure the

Re: [PD] Purr Data beta 2

> You’ll probably need to build form source in either environment if you want > to be > sure of the deployment target. Both Homebrew and Macports are focused on > running OS software for the current system, much less so for building baked > libraries to run on other systems. Ok, so I tried out

Re: [PD] Purr Data beta 2

As a blanket answer that may be true as that’s not the goal of the project, but technically, it’s totally possible depending on what you’re building. In the end, it’s all just C/C++ libraries you *could* download and build yourself. The same is true for different versions of Linux distros.

Re: [PD] Purr Data beta 2

> You’ll probably need to build form source in either environment if you want > to be sure of the deployment target. Both Homebrew and Macports are focused > on running OS software for the > current system, much less so for building baked libraries to run on other > systems. >From

Re: [PD] Purr Data beta 2

s.iem.at> Sent: Monday, October 10, 2016 3:18 PM Subject: Re: [PD] Purr Data beta 2 I get this when trying to download beta 2 for mac https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-osx64-beta2.zip 404 The page you're looking for could not be found. 2016-10-

Re: [PD] Purr Data beta 2

I get this when trying to download beta 2 for mac https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-osx64-beta2.zip 404 The page you're looking for could not be found. 2016-10-10 15:26 GMT-03:00 Dan Wilcox : > Well, the deployment target only

Re: [PD] Purr Data beta 2

Well, the deployment target only *indicates* to the OS if the app should be runnable. It also helps in defining which APIs are allowed. In either, case it’s no guarantee but, if a project is not using anything too new or esoteric, it can run fine on a lot of different versions of systems. In

Re: [PD] Purr Data beta 2

> You’ll probably need to build form source in either environment if you want > to be sure of the deployment target. Both Homebrew and Macports are focused > on running OS software for the current > system, much less so for building baked libraries to run on other systems. I'm also just

Re: [PD] Purr Data beta 2

You’ll probably need to build form source in either environment if you want to be sure of the deployment target. Both Homebrew and Macports are focused on running OS software for the current system, much less so for building baked libraries to run on other systems. Dan Wilcox

Re: [PD] Purr Data beta 2

> Judging from the output of brew —env, there is a MACOSX_DEPLOYMENT_TARGET you > should be able to set/override. Simplest way would be when running brew: >     MACOSX_DEPLOYMENT_TARGET=10.6 brew … > That, in combination with —build-from-source when installing packages, might > give you want

Re: [PD] Purr Data beta 2

Judging from the output of brew —env, there is a MACOSX_DEPLOYMENT_TARGET you should be able to set/override. Simplest way would be when running brew :

Re: [PD] Purr Data beta 2

> The closest might be -universal which asks to build/install a universal 32/64 > bit package. There might be something else, but you’ll need to check the > docs: http://brew.sh Nothing pops out at me.  It would be an enormous benefit over Macports-- which doesn't officially support targeting

Re: [PD] Purr Data beta 2

;danomat...@gmail.com> > Cc: Pd-List <pd-list@lists.iem.at> > Sent: Monday, October 10, 2016 9:31 AM > Subject: Re: [PD] Purr Data beta 2 > > > Thank you. /usr/local always seems iffy to me, but this is after years in > > linux > > making sure to mak

Re: [PD] Purr Data beta 2

> Does Homebrew require XCode? If so then speed of package installs is > insignificant by comparison. > > If not then I'll give it a try-- that would reduce the total time to build > from 1 day to > something less obnoxious. Yes and no. Yes in that you need to install the Xcode Commandline

Re: [PD] Purr Data beta 2

cox <danomat...@gmail.com> Cc: Pd-List <pd-list@lists.iem.at> Sent: Monday, October 10, 2016 9:31 AM Subject: Re: [PD] Purr Data beta 2 > Thank you. /usr/local always seems iffy to me, but this is after years in > linux > making sure to make packages to install

Re: [PD] Purr Data beta 2

h all of the libs y’all install via macports > > are available in Hombrew. > > > > > > Dan Wilcox > > @danomatika > > danomatika.com > > robotcowboy.com > > > > > On Oct 9, 2016, at 11:35 PM, pd-list-requ...@lists.iem.at

Re: [PD] Purr Data beta 2

> Thank you. /usr/local always seems iffy to me, but this is after years in > linux > making sure to make packages to install any software via package manager. The > thing I liked about macport's /opt, which is actually something of a standard > for > non-pacakge-managed software in linux, is

Re: [PD] Purr Data beta 2

t; danomatika.com > robotcowboy.com > > On Oct 9, 2016, at 11:35 PM, pd-list-requ...@lists.iem.at wrote: > > *From: *IOhannes m zmölnig <zmoel...@iem.at> > *Subject: **Re: [PD] Purr Data beta 2* > *Date: *October 9, 2016 at 3:20:17 PM MDT > *To: *pd-list@lists.iem.at >

Re: [PD] Purr Data beta 2

otcowboy.com <http://robotcowboy.com/> > On Oct 9, 2016, at 11:35 PM, pd-list-requ...@lists.iem.at wrote: > > From: IOhannes m zmölnig <zmoel...@iem.at <mailto:zmoel...@iem.at>> > Subject: Re: [PD] Purr Data beta 2 > Date: October 9, 2016 at 3:20:17 PM MDT > To: p

Re: [PD] Purr Data beta 2

On 10/09/2016 11:09 PM, Matt Barber wrote: > Thanks for this, IOhannes. We've been using macports for most of the > development of purr-data on OSX (with a couple of fink installs for some > libraries). Do you find brew to be superior, or was this a comfortable > default? i cannot really remember

Re: [PD] Purr Data beta 2

Thanks for this, IOhannes. We've been using macports for most of the development of purr-data on OSX (with a couple of fink installs for some libraries). Do you find brew to be superior, or was this a comfortable default? Thanks, Matt On Sun, Oct 9, 2016 at 5:05 PM, IOhannes m zmölnig

Re: [PD] Purr Data beta 2

On 10/07/2016 03:35 AM, Jonathan Wilkes via Pd-list wrote: > What configure flags do I need to successfully build this? what errors do you get? try "--without-QuickTime-framework --without-Carbon-framework" or simile. or just read the wiki[1] fgmasrd IOhannes [1]

Re: [PD] Purr Data beta 2

> Sure but it’s often easier to have/start a discussion with a proposed/working > solution. Did this involve changes to the pd core or are you wrapping the > lower level apis? Changes to the core. -Jonathan ___ Pd-list@lists.iem.at mailing list

Re: [PD] Purr Data beta 2

Sure but it’s often easier to have/start a discussion with a proposed/working solution. Did this involve changes to the pd core or are you wrapping the lower level apis? Dan Wilcox @danomatika danomatika.com robotcowboy.com

Re: [PD] Purr Data beta 2

> Sweet! :) Ok, awesome. You’re ahead on this. Just to be clear-- that spec isn't a future proposal.  It's implemented in Purr Data. -Jonathan ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->

Re: [PD] Purr Data beta 2

Sweet! :) Ok, awesome. You’re ahead on this. Dan Wilcox @danomatika danomatika.com robotcowboy.com > On Oct 6, 2016, at 3:49 AM, pd-list-requ...@lists.iem.at >

Re: [PD] Purr Data beta 2

On Oct 6, 2016, at 3:49 AM, pd-list-requ...@lists.iem.at wrote: 1) External developers who want to support purr-data (pd-l2ork) can #ifdef their guis.2) For those who don't want to learn a new toolkit, and for unmaintained libraries, it'll be up to purr-data developers. Until we have good

Re: [PD] Purr Data beta 2

As a follow up: this approach is what we’ve taken with libpd and it’s worked very well so far. Peter initially discussed with Miller what changes and api access would be needed to wrap libpd. Once those were in place, the rest of libpd is essentially just wrappers around the vanilla core

Re: [PD] Purr Data beta 2

> On Oct 6, 2016, at 3:49 AM, pd-list-requ...@lists.iem.at wrote: > > 1) External developers who want to support purr-data (pd-l2ork) can #ifdef > their guis. > 2) For those who don't want to learn a new toolkit, and for unmaintained > libraries, it'll be up to purr-data developers. > > Until

Re: [PD] Purr Data beta 2

> On 10/06/2016 04:26 PM, Jonathan Wilkes via Pd-list wrote: >> >>> > (Gem: can't load library) >> Gem currently requires deprecated Apple libs.  Those libs require Gem to >> be built for i386 arch. > not really true. > Gem can be built fine on OSX/x86_64. > the only things that cannot be

Re: [PD] Purr Data beta 2

​The deprecated library in question is Carbon, which is 32-bit only. I can't remember whether or not there were plans to update Gem to use Cocoa instead, but if I remember correctly it was going to require some major surgery. There are also tons of problems in the Gem code elsewhere that ​clang

Re: [PD] Purr Data beta 2

> Is there any chance to get Gem working with Purr Data on OS X? > (Gem: can't load library) Gem currently requires deprecated Apple libs.  Those libs require Gem to be built for i386 arch.  Building Gem that way would require building all of Purr Data for i386 arch. When I tried changing

Re: [PD] Purr Data beta 2

Is there any chance to get Gem working with Purr Data on OS X? (Gem: can't load library) Volker Am 06.10.16 um 02:53 schrieb Jonathan Wilkes via Pd-list: Here's an update for the OSX binary (Beta 1.2): https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-osx64-beta2.1.zip

Re: [PD] Purr Data beta 2

Here's an update for the OSX binary (Beta 1.2):https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-osx64-beta2.1.zip This fixes an error that kept Pd from starting, as well as adding a missing dependency to get pdp working. Unfortunately I couldn't get the jack backend

Re: [PD] Purr Data beta 2

Yep, that's something I'm thinking about carefully and will work with Jonathan on in the coming days. I made some huge updates to scope~ over the summer as well which need to be ported, and [comment] needs that also (although there are some cross-platform font size bugs to take care of on cyclone

Re: [PD] Purr Data beta 2

> Jonathan and Alexandre, > coll text editor with all its legacy pdtk calls is inoperable inside > purr-data. > Cyclone and other extern libraries with GUIs may require an ifdef for > purr-data (or > preferably pd-l2ork) and appropriate adaptation. Is there a public interface for the

Re: [PD] Purr Data beta 2

Jonathan and Alexandre, coll text editor with all its legacy pdtk calls is inoperable inside purr-data. Cyclone and other extern libraries with GUIs may require an ifdef for purr-data (or preferably pd-l2ork) and appropriate adaptation. Best, Ico On 10/5/2016 12:56 AM, Jonathan Wilkes via

[PD] Purr Data beta 2

This is the beta 2 release of Purr Data (the GUI port of Pd-l2ork) Change log: * compatibility with older osx versions * fix external library dependencies on OSX * first try at jack support for OSX * more fixes for out-of-order messages to GUI * fix crasher on Windows when opening a help patch *