I also created single object binary versions of all these objects with
their alphanumeric version/alias, and they all have individual help files -
perhaps I'll just keep them and delete the others
thanks
2016-04-10 9:29 GMT-03:00 katja :
> I notice there used to be one
I notice there used to be one help patch indeed for all nettles, as in
Fred Jan's version. For a good reason as we now see. Alexandre has
created individual help patches for each nettles class. These could
better be encapsulated within nettles-help.pd, rather than live as
separate files.
Katja
Hello Derek,
The problem is with the following help files added by Alexandre:
<~-help.pd
<=~-help.pd
>~-help.pd
>=~-help.pd
You could filter these out from the wildcard search in the makefile
and instead list them explicitly, between quotes like:
"help/<~-help.pd"
Alternatively you could make
2016-04-09 11:47 GMT-03:00 Jonathan Wilkes :
> Try testing without loading any libraries at startup.
>
that's what I was doing in the first place, been using a clean vanilla with
no libs installed, but I re checked and all
About documentation, this issues can be addressed in
yeah, there are, and I had forgotten about them, it's a good thing katja
pointed it out. Check at the very bottom; here's what it looks like now:
##
cyclone extra targets ##
install:
Hello Derek,
The symlinks aren't created at compile time but during the install
process. It is done by target 'install-aliases'. Do 'make install
objectsdir=./build' to get a local install. If you still get no
symlinks let me know.
I think they are only needed on Linux because of how file access
> On Fri, Apr 8, 2016 at 10:52 PM, IOhannes m zmölnig wrote:
> > On 04/08/2016 10:29 PM, Alexandre Torres Porres wrote:
> >> Then, cyclone does not come as a library for a long time, and "Scope~" is
> >> not part of a "-lib"
> >
> > but it is!
> > it is part of a library named
ok, but let me be picky... first, [declare -lib] loads a library, relative
to the patch, so there seems to be no reason to declare it if it is in the
same folder as the patch and I could just call it by [./scope~], right?
But well, if you actually mean using [declare -stdlib], same thing goes...
On 04/09/2016 12:06 AM, Alexandre Torres Porres wrote:
> sure, but not a library containing many objects, so I don't see why using
> [declare -lib], isn't that just for the case of libraries with many
> objects? Since it is just a single object binary, all I need is to have it
> in a path, so more
2016-04-08 17:52 GMT-03:00 IOhannes m zmölnig :
> On 04/08/2016 10:29 PM, Alexandre Torres Porres wrote:
> > Then, cyclone does not come as a library for a long time, and "Scope~" is
> > not part of a "-lib"
>
> but it is!
> it is part of a library named "Scope~.pd_linux" which
On Fri, Apr 8, 2016 at 10:52 PM, IOhannes m zmölnig wrote:
> On 04/08/2016 10:29 PM, Alexandre Torres Porres wrote:
>> Then, cyclone does not come as a library for a long time, and "Scope~" is
>> not part of a "-lib"
>
> but it is!
> it is part of a library named
Alexandre, it seems you found a good approach to gradually phase out
upper case (when not needed to avoid name clash). If you change class
name and aliases the C code don't forget to swap upper / lower case in
the symlinks too, which are created for Linux under 'cyclone extra
targets' in the
On 04/08/2016 10:29 PM, Alexandre Torres Porres wrote:
> Then, cyclone does not come as a library for a long time, and "Scope~" is
> not part of a "-lib"
but it is!
it is part of a library named "Scope~.pd_linux" which contains a single
object "Scope~".
mdsf
IOhannes
signature.asc
2016-04-08 16:11 GMT-03:00 Jonathan Wilkes :
> if the user isn't loading cyclone by default, and their patch does this:
> [declare -lib cyclone/Scope~]
>
Ok, but what would that do in the first place? I don't think I get
[declare] yet, can you find a specific individual
I don't think that's backwards compatible. For example-- if the user isn't
loading cyclone by default, and their patch does this:
[declare -lib cyclone/Scope~]
[Scope~]
***
If by "traded" you mean you renamed the binary to scope~.pd_linux, this won't
load anymore.
I'd actually be in favor of
2016-04-06 18:53 GMT-03:00 Alexandre Torres Porres :
> And what would change if the official name restores to scope~ (with Scope~
> being called the way "scope~" is now?
>
Well, I tested it here... I traded it for the opposite. I changed "Scope~"
to "scope~" and made it
2016-03-30 4:53 GMT-03:00 IOhannes m zmoelnig :
> [Scope~] did solve the nameclash after all, even if you build cyclone as
> a set of single-object-externals and deployed on a case-insensitive
> filesystem.
>
well, we don't need to solve that anymore. And by the way, nowadays
pdrunsonwindowstoo
maybe windows is/was not that case sensitive?
> On 30 Mar 2016, at 09:53, IOhannes m zmoelnig wrote:
>
>> pdrunsonwindowstoo
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
On 2016-03-30 00:03, Jonathan Wilkes via Pd-list wrote:
> Yes, there's a very good reason to employ a solution to a name clash.
> Also, using a capital letter in an external name is a poor solution to that
> problem. Even calling the thing "pdrunsonwindowstooscope~" would have
well, yes or
19 matches
Mail list logo