Well, that's not my decision. So it seems, using a "." to seperate prefixes from names doesn't work with older Pd's unless it's just an alternate name (created with class_addcreator), right?
So the other easy fix would be to use "sp_" instead of "sp."
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
salut thats right "sp." works only as library so why not compile it as library?? gruss m.weiss
Hallo, m.weiss hat gesagt: // m.weiss wrote:
So the other easy fix would be to use "sp_" instead of "sp."
thats right "sp." works only as library so why not compile it as library??
So why not use "sp_"? ;)
The debate about single externals vs. libraries has be fought often in the past, I don't want to start it again. However when using "sp." effectively inhibits building as single externals, I would vote for changing this one letter. I already did it in attached archive, together with some other changes as described in CHANGES. What do you think?
Frank Barknecht _ ______footils.org_ __goto10.org__
Frank Barknecht schrieb:
Hallo, m.weiss hat gesagt: // m.weiss wrote:
So the other easy fix would be to use "sp_" instead of "sp."
thats right "sp." works only as library so why not compile it as library??
So why not use "sp_"? ;)
The debate about single externals vs. libraries has be fought often in the past, I don't want to start it again. However when using "sp." effectively inhibits building as single externals, I would vote for changing this one letter. I already did it in attached archive, together with some other changes as described in CHANGES. What do you think?
Ciao
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
salut ok for compatibility this is the best way we take "sp_" i change my release and include single objects and also the complete library for win32 so everybody can go his own way for loading these stuff can you mail or send me a link to the ported lib so i can post it on my site would be great thanks gruss m.weiss
salut ok for compatibility this is the best way we take "sp_" i change my release and include single objects and also the complete library for win32 so everybody can go his own way for loading these stuff can you mail or send me a link to the ported lib so i can post it on my site
harr harr i take the one attached ok? definetely working too much thanks for your work frank gruss m.weiss
so what's the chance of getting this up for osX ?? looks great
your tracks sound good too weiss
;)
It'll be in Pd-0.38.4-extended-RC7 coming soon. You can compile it
from CVS too, either:
cd externals && make sigpack
OR
cd externals/sigpack && make
Then they'll be compiled as single files rather than a lib. This works
on Mac OS X, GNU/Linux, and MinGW/Windows.
.hc
On Jan 11, 2006, at 7:46 AM, hard off wrote:
so what's the chance of getting this up for osX ?? looks great
your tracks sound good too weiss
;)
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism."
- retired U.S. Army general,
William Odom
hard off schrieb:
so what's the chance of getting this up for osX ?? looks great
should be no problem but i havent any expirience with macs and no machine maybe someone can port this to mac ill post it on my side too
your tracks sound good too weiss
thanks gruss m.weiss
On Jan 7, 2006, at 7:16 AM, m.weiss wrote:
Well, that's not my decision. So it seems, using a "." to seperate prefixes from names doesn't work with older Pd's unless it's just an alternate name (created with class_addcreator), right?
So the other easy fix would be to use "sp_" instead of "sp."
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
salut thats right "sp." works only as library so why not compile it as library?? gruss m.weiss
With the Pd-extended builds, there is a functional namespace. So the
sp. prefix is unnecessary. It also is kind of ugly and makes the
object names needlessly longer.
Mind if I remove the sp. prefix when I import it to CVS? I can leave
the library with the sp.* names so just the single objects will be
without.
.hc
News is what people want to keep hidden and everything else is
publicity.
- Bill Moyers
On Sat, 7 Jan 2006 10:47:53 -0500 Hans-Christoph Steiner hans@eds.org wrote:
Mind if I remove the sp. prefix when I import it to CVS? I can leave the library with the sp.* names so just the single objects will be without.
well, after reading this, i thought, that the sp. prefix is only removed for single objects? looking at the cvs, it seems, there is no way to build it as library with sp. prefix, nor is it possible to build it without the external build system.
i'm not sure, if this is the right way to add code to the cvs ... some people avoid the external build system and prefer libraries ...
t
On Jan 17, 2006, at 9:00 PM, Tim Blechmann wrote:
On Sat, 7 Jan 2006 10:47:53 -0500 Hans-Christoph Steiner hans@eds.org wrote:
Mind if I remove the sp. prefix when I import it to CVS? I can leave the library with the sp.* names so just the single objects will be without.
well, after reading this, i thought, that the sp. prefix is only removed for single objects? looking at the cvs, it seems, there is no way to build it as library with sp. prefix, nor is it possible to build it without the external build system.
i'm not sure, if this is the right way to add code to the cvs ... some people avoid the external build system and prefer libraries ...
t
Feel free to add whatever you want, as long as existing functionality.
I just did what I said I would, I don't see the need for multiple build
systems. You can download the source and binary of the sp. prefix
library from the sIgpAck site still if that suits you better.
.hc
¡El pueblo unido jamás será vencido!
i don't want to start a flamewar, so this will be my last posting on this topic ...
Feel free to add whatever you want, as long as existing functionality. I just did what I said I would, I don't see the need for multiple build systems.
its not about multiple build systems, but about multiple ways of using the code:
by changing the sources, you already decided to kick the prefix and build it as single externals (maybe you removed the prefix to make it possible to use them as single externals)
You can download the source and binary of the sp. prefix library from the sIgpAck site still if that suits you better.
i don't think, the reason of the cvs is to have a build system, but to have all sources in one place ... thus i don't want to go to the website to download and build the library, if i have all the sources on my machine ...
anyway, you'll do what you want in any case, just note, that there are other people, who are using the cvs, too
tim
On Jan 18, 2006, at 7:30 AM, Tim Blechmann wrote:
i don't want to start a flamewar, so this will be my last posting on this topic ...
Feel free to add whatever you want, as long as existing functionality. I just did what I said I would, I don't see the need for multiple build systems.
its not about multiple build systems, but about multiple ways of using the code:
- prefix vs. no prefix
- library vs. single externals
by changing the sources, you already decided to kick the prefix and build it as single externals (maybe you removed the prefix to make it possible to use them as single externals)
You can download the source and binary of the sp. prefix library from the sIgpAck site still if that suits you better.
i don't think, the reason of the cvs is to have a build system, but to have all sources in one place ... thus i don't want to go to the website to download and build the library, if i have all the sources on my machine ...
anyway, you'll do what you want in any case, just note, that there are other people, who are using the cvs, too
I am not preventing anyone from doing things how they want. But don't
ask me to do the work for other people's setups. I don't use
single-file libraries, so I don't see why I would be expected to
maintain single-file libraries.
Like I said before, feel free to add whatever you need, just don't
break what's there.
.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