[PD] [Scope~] (was Re: can signal inlets that aren't the main inlet have float or message methods?)

[Alexandre Torres Porres]

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: install-aliases

# on Linux, add symbolic links for UPPER case aliases

install-aliases: all

ifeq ($(uname), Linux)

$(INSTALL_DIR) -v $(installpath)

cd $(installpath); \

        ln -s -f Append.$(extension) append.$(extension); \
        ln -s -f Append-help.pd append-help.pd; \


I haven't changed Append yet, but here's how scope is now:

 ln -s -f scope~.$(extension) Scope~.$(extension); \
 ln -s -f scope~-help.pd Scope~-help.pd; \


Please recompile and test putting [Scope~] or [cyclone/Scope~]


cheers

2016-04-09 7:01 GMT-03:00 Derek Kwan <derek.x.kwan at gmail.com>:

> > On Fri, Apr 8, 2016 at 10:52 PM, IOhannes m zmölnig <zmoelnig at iem.at>
> 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 "Scope~.pd_linux" which contains a single
> > > object "Scope~".
> >
> > He's building 'scope~.pd_linux'. With a symlink 'Scope~.pd_linux' and
> > the alias in the C code, wouldn't that be all right?
> > >
> > > mdsf
> > > IOhannes
> > >
> >
>
> Hello,
>
> I'll chime in here because I've been working on this cyclone update as
> well (Alexandre, hop in here if I'm wrong about any of this). To my
> knowledge, there isn't any symlinking going on in the build process. I'm
> using Ubuntu on my machine and I just built it myself and all I get out
> for scope is scope~.pd_linux. All references to Scope has been changed
> to scope in Makefile and the source (sickle/Scope.c) got changed to
> sickle/scope.c. There's no symlink to scope~.pd_linux at all. Do we want
> to change the Makefile to build a symlink to the built scope~ (and also,
> what are the reasons for doing so)? Also. is there a symlink equivalent
> for Windows machines? I'll be honest, I'm not really familiar with
> Makefile building beyond the very basic stuff (I didn't even know you
> could make symlinks in Makefiles for instance)...
>
> Derek
>
> =====================
> Derek Kwan
> www.derekxkwan.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160409/38b71035/attachment-0001.html>