Am 09.11.2005 um 12:15 schrieb David Plans Casal:
just think about this possible scenario:
- install pd + externals via package management (fink/darwinports)
+1
- run a script which grasps all the abstractions and .pd_darwins
- docs.
From where? I mean once you've installed with 'fink install pd' or
whatever, how do you envision running the script?
i imagine something like pdadmin or phps pdmkapp you mentioned below.
I was just thinking of one big Pd.app being dumped in / Applications, with all needed externals pre-built.
cool. this will be step 1.
- run a script which grasps all the needed dylib's from the
distribution (using "otool -L")
Interesting.
but sadly not quite straight forward. see http://qin.laya.com/ tech_coding_help/dylib_linking.html
this mechanism could be extended to provide a way to easily deploy
custom Pd.app which just include needed externals and possibly
have patches autostarted.Ok so we could have CLI instructions such as:
'pdadmin myinstallation'
And output would be a myinstallation.app/ directory with pd
binaries, externals, etc? I guess CLI options to that would be
nice. A bit like Django and Rails options.Not sure though, how one would go about building this.
me neither. just ideas.
@hans+james. this is no rant against you and i don't want to just
create another build system. i'm just thinking about how pd on mac
could be more conveniant for (doubleclick)users AND (cli) developers :)And yes, why not rely on the current build systems?
don't know how they will go with fink.
Anyway, I think it's a good idea overall!
d
-- # David Plans Casal
problem.each { |day| assert_nil(spoon) }
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list