On May 1, 2005, at 11:47 PM, Mathieu Bouchard wrote:
On Wed, 27 Apr 2005, Hans-Christoph Steiner wrote:
How about importing a stable version of GridFlow into the pure-data
CVS? Then we can include GridFlow as part of the Pd.app build system.
Its quite simple, once its in CVS, you make a gridflow target that
does everything needed to compile gridflow. Then copy the files to
the Pd.app, then it'll be part of all future Pd.app builds.It will be an unstable version actually. I'll pick whatever's in the
CVS right now, and call it 0.8.0, and that will go in the pure-data
CVS.The last stable release of GridFlow, 0.7.7, is getting a bit old, and
a lot of 0.7 ways are getting deprecated, so I wouldn't want to
encourage newbies to use it.OTOH, GridFlow 0.8.0 has a bunch of bugs, which is not
newbie-friendly. But whatever. I think that publishing 0.8.0 as-is
will encourage me to make 0.8.1 much more stable and release it
quickly...
Give me a holler if you want help with the Pd.app build system. What
you need to do is quite straightforward: just make a Makefile target
that executes whatever is necessary to build gridflow. I'd say
externals/gridflow is a good spot for it. We should probably set up an
ACL so that if people want to commit changes to CVS, they'll have to
make a branch (that's the way other imported sources are setup).
Also, you should include whatever libs/frameworks/etc. that
OSX/Debian/etc. doesn't normally provide (for example, if you use that
Ruby.framework). I think that the Apple Developer tools include ruby
dev files now. Or at least my computer has
/usr/lib/ruby/1.6/powerpc-darwin7.0/ruby.h
.hc
"Looking at things from a more basic level, you can come up with a more
direct solution... It may sound small in theory, but it in practice, it
can change entire economies."
- Amy Smith