Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On May 5, 2009, at 12:09 PM, Steffen Juul wrote:
On 02/05/2009, at 3.31, Hans-Christoph Steiner wrote:
So here's the solution i came up with, you make a 'lib' folder in your project, stick the libraries as folders
in 'lib', then use [declare -path lib]. Here's an example:But what about "sorry, couldn't find help patch for "mapping/ curve.pd"" ?
I should have said, due to bugs in [declare], this only works on GNU/ Linux. Since Miller uses Linux, I was assuming that its the reference
platform in terms of how [declare] works. It currently works
differently/less on Mac OS X, for example.
What are these differences? In our RjDj sprints, most people use OS-X with no problems, and on Linux, the help files still aren't found either - which is a known issue of directory prefixes since ages: You have to set the help-path as well.
But if libraries have complicated interdependencies or assume certain global path layouts, then this approach fails, which was the case with the
old mapping files, at least partly.Part of my point with this examples is to show that you can have a
simple setup while using namespace prefixes in the project, libraries as folders, and in the libraries that a project uses. I couldn't find any issues with the setup illustrated in that tarball, have you found some?
"mapping" still assumes that it is installed in a subdirectory called "mapping" whose parent is in the search path. It's not possible for a user to just drop the patches from "mapping" into her project folder directly or into a differently named subdir made know with declare. A user has to mimick the directory layout set in mapping. And do so for purepd as well. That's not a problem with the tarball, it just a - deliberate - restriction of "mapping".
Ciao
Frank