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 that it's

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

On Mon, 2016-10-10 at 09:13 -0400, Matt Barber wrote: > 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. /usr/local [1] is exactly meant for _local_ installations that do not interfere

[PD] Question about the pd-extended history

Does anyone have a link to a paper or a publication that documents the motivation behind and original initiators of the pd-extended? I traced releases back to 2003 but there is no info on who were original players who started it. Thank you. Best, -- Ivica Ico Bukvic, D.M.A. Associate

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] Question about the pd-extended history

I'm curious to know which were (all) the releases and the dates they were released 2016-10-10 15:07 GMT-03:00 Jonathan Wilkes via Pd-list : > > Does anyone have a link to a paper or a publication that documents the > > > > motivation behind and original initiators of the

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] Question about the pd-extended history

> Does anyone have a link to a paper or a publication that documents the > motivation behind and original initiators of the pd-extended? I traced > releases back to 2003 but there is no info on who were original players > who started it. Thank you. Didn't Hans start it? > Best, -- Ivica

Re: [PD] Question about the pd-extended history

On 10/10/2016 2:07 PM, Jonathan Wilkes wrote: > Does anyone have a link to a paper or a publication that documents the > motivation behind and original initiators of the pd-extended? I traced > releases back to 2003 but there is no info on who were original players > who started it. Thank you.

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

> 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

I had to push a quick update to fix a freezer bug. Try:https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-osx64-beta2.1.zip -Jonathan From: Alexandre Torres Porres To: Jonathan Wilkes Cc: Pd-List

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.

[PD] MIDI issue with Purr Data beta 2 or Pd-Extended

Howdy, anybody ever had a problem with MIDI input in PD where it would always send a "zero" value from a korg keyboard controller? A student of mine was having this problem, we tested it with Data beta 2 and Pd-Extended, same issue but it worked on vanilla 0.47-1 tested with mac and windows...

Re: [PD] Question about the pd-extended history

> On 10/10/2016 2:07 PM, Jonathan Wilkes wrote: > >> Does anyone have a link to a paper or a publication that documents the > > > > > >> motivation behind and original initiators of the pd-extended? I traced > >> releases back to 2003 but there is no info on who were original players > >> who

Re: [PD] Purr Data beta 2

One more Homebrew question:Does homebrew let me do the equivalent of -mmacosx-version-min ?  Can I ask it for a libsdl package that runs on 10.4 and greater? -Jonathan From: Jonathan Wilkes via Pd-list To: Matt Barber ; 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 :

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

> 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

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 FYI currently the portaudio package cannot build for universal due to a configure check. Dan