-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-02 13:01, Patrice Colet wrote:
I've found the odd part of that page is that they use LTLIBRARIES variable
while pd/src/Makefile.am doesn't.
does this mean that you have had no success with the dummy.cpp file
(output?) or that you
://enigmail.mozdev.org/
iEYEARECAAYFAk4avYkACgkQkX2Xpv6ydvTwPACeOmrqMSLAdz/YA+68e4zgWYHO
cZcAn32FOZOtnyIsGBoDfSDq/xYwwFFX
=Djnx
-END PGP SIGNATURE-
From 18878d89cfe3b02ff2649b48b6a9902fd1d0a4de Mon Sep 17 00:00:00 2001
From: IOhannes m zmoelnig zmoel...@iem.at
Date: Mon, 11 Jul 2011 11:00:21 +0200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-11 17:59, Hans-Christoph Steiner wrote:
We have the opposite problem than that automake hack is trying to
solve. When ASIO is including, then everything including portaudio is
built and linked using g++. Portaudio fails to build with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-11 19:02, Patrice Colet wrote:
- Patrice Colet colet.patr...@free.fr a écrit :
The problem I'm encountering on win32 with makefile.am is that pd.dll
is not built
if I add this:
if WINDOWS
LIBS += -lwsock32 -lwinmm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-11 19:37, Hans-Christoph Steiner wrote:
That makes me think so ./configure is finding libdl find, and then
setting HAVE_LIBDL, and then the code in s_loader.c is going to do both
HAVE_LIBDL and the MSW section below it. So I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-11 23:20, SourceForge.net wrote:
Message:
Ok, I added this to Pd-extended. Be very careful to not copy things that
are not being translated. I.e. if DSP is going to remain DSP, then it
should look like this:
msgid DSP
msgstr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-13 14:20, Nicolas Montgermont wrote:
Before going further (tabread~, tabread4,...) I wanted to know if
someone has already done something similar or if you have advices on
names and behavior.
i think thomas musil did something like a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-13 15:30, Nicolas Montgermont wrote:
Le 13/07/11 14:29, IOhannes m zmoelnig a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-13 14:20, Nicolas Montgermont wrote:
Before going further (tabread~, tabread4,...) I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-13 19:31, katja wrote:
On Wed, Jul 13, 2011 at 3:51 PM, IOhannes m zmoelnig zmoel...@iem.atwrote:
the idea is to make double the standard for Pd in the future.
if nobody spents time for that it will never happen.
I'd like to help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-07-13 20:11, Jonathan Wilkes wrote:
Hello,
Why is struct _canvasenvironment in g_canvas.c instead of g_canvas.h?
I want to take a t_object inside g_text.c and-- if it's an abstraction-- get
its name and dir. I can get the name but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-10 03:42, Rick T wrote:
# Makefile
# (c) 2006 IOhannes m zmölnig
oh, where did you get that one from?
nowadays, i would recommend using the Makefile template as found in
externals/template
(i should change the build system in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-26 14:14, Roman Haefeli wrote:
On Thu, 2011-09-22 at 17:36 -0400, Hans-Christoph Steiner wrote:
Hey IOhannes,
I think iemguts is ready primetime, I think it should be included in
the next Pd-extended 0.43 release. Do you have any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-26 23:29, Hans-Christoph Steiner wrote:
My guess is that it'll be something like this:
#ifdef _WIN32
PATH
#elif defined(__APPLE__)
DYLD_LIBRARY_PATH
#else
LD_LIBRARY_PATH
#endif
i would go for something with less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cocoaconvert.net/2009/08/02/frameworks-with-private-frameworks/
fgmasdr
IOhannes
___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-29 17:15, Hans-Christoph Steiner wrote:
Hey Roman,
I just saw this commit:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/Makefile?r1=15393r2=15397
.la files generally should not be installed, that makes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-29 17:41, Hans-Christoph Steiner wrote:
What is the problem this is trying to solve? How are the .la files
causing problems ? The Pd-extended is crufty enough as it is with lots
of kludges like this that I'm mostly responsible for.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
@pd-dev: in the course of making packages for debian, we discovered
another slight problem with the -stdpath and -stdlib flags for
declare (and probably this also expands to the -nostdpath startup
flag). following is an excerpt of the discussion in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
when i try to login to the machine, i get:
Uptime for this computer is 10 [main] gawk 2200
C:\cygwin\bin\gawk.exe: *** fatal error - CreateFileMapping
Global\cygwin1S4.cygpid.3780, Win32 error 5. Terminating.
and i don't get a shell, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 11:49, IOhannes m zmoelnig wrote:
when i try to login to the machine, i get:
Uptime for this computer is 10 [main] gawk 2200
C:\cygwin\bin\gawk.exe: *** fatal error - CreateFileMapping
Global\cygwin1S4.cygpid.3780, Win32 error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 16:31, Hans-Christoph Steiner wrote:
These all sound like good ideas to try. My only concern is that we
might let the deployment issues distract from the issues at hand about
getting it actually working first.
i'm definitely with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 17:16, Roman Haefeli wrote:
On Mon, 2011-10-03 at 10:47 -0400, Hans-Christoph Steiner wrote:
Looks like it was set to Pending, do you still need help with it?
No, that is what I am saying. It can be closed. But I seem to lack the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 17:44, katja wrote:
Thanks IOhannes for all your comments and suggestions.
I just realized that there are several ways in which identical symbols
for different function definitions could cause a problem and I did not
distinguish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 18:00, Charles Henry wrote:
Would you prefer to set the types at configure time through a file--or
for example by adding a -DDOUBLE compiler flag? The affected
locations of code defining the types could just use #ifdef DOUBLE
no,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 18:04, katja wrote:
On Mon, Oct 3, 2011 at 4:35 PM, Hans-Christoph Steiner h...@at.or.at wrote:
Do you have access to an ARM
machine? If not, I could probably get one online with ssh access, if that's
useful.
I've mailed Joe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 18:32, Hans-Christoph Steiner wrote:
More on actually trying the patch. I tried to apply it to the HEAD of
pure-data.git, and one section failed:
pd@debian-lenny-i386 src $ patch -p1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
I don't really know why this is happening, but I do know that the
./autogen.sh in pure-data.git and pd-extended.git works everywhere since
it is used in the builds every night. Why not just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 19:19, IOhannes m zmoelnig wrote:
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
I don't really know why this is happening, but I do know that the
./autogen.sh in pure-data.git and pd-extended.git works everywhere since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-04 11:19, Roman Haefeli wrote:
Applied to standard paths this would lead to the following search order:
1) ~/pd-externals
2) /usr/local/lib/puredata/extra
3) /usr/local/lib/pd/extra
4) /usr/lib/puredata/extra
5) /usr/lib/pd/extra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
On Oct 3, 2011, at 5:06 AM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-02 22:27, Hans-Christoph Steiner wrote:
FYI:
http://autobuild.puredata.info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-05 18:16, Hans-Christoph Steiner wrote:
On Oct 5, 2011, at 4:05 AM, IOhannes m zmoelnig wrote:
The logfile I see says its set to:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin
http://autobuild.puredata.info/auto-build/2011
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-15 04:08, Patrice Colet wrote:
also I've added
CXX=g++
because i'm using mingw, and it starts compile :)
hmm, what is the default for CXX on mingw?
i think it's a bad idea to hardcode the used compiler for no compelling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-17 17:11, Patrice Colet wrote:
Hello IOhannes,
all I could say is this:
$ make -p -n | grep CXX
make: *** No targets specified and no makefile found. Stop.
LINK.cc = $(CXX) $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-18 05:01, Patrice Colet wrote:
then you did something weird :-)
i had the same problem after changing CC to CXX and replacing
myobject.c
with myobject.cpp
the template/Makefile is full of assumptions that the sources end
with
.c;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-18 05:01, Patrice Colet wrote:
Also I still have same question about pd includes, but more accurately...
i missed that question :-)
gui externals needs m_imp.h, because of this:
[...]
c_externdir-s_name and c_name-s_name are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-17 22:27, katja wrote:
There's however a small issue to reckon with: at the moment, the only
way to force double precision compilation upon the external libs, is
to hardcode #define PF_FLOAT_PRECISION 64 in m_pd.h. If we put it in
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-18 22:16, katja wrote:
On Tue, Oct 18, 2011 at 8:33 PM, Hans-Christoph Steiner h...@at.or.at wrote:
Another idea for handling this is to use the ./configure
--enable-double-precision flag, but have it generate a config.h, which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-19 01:29, Hans-Christoph Steiner wrote:
Yes! I got it working. I see the way to use it for this situation,
this looks like great news!
fgmadr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-19 21:07, Hans-Christoph Steiner wrote:
I don't really understand what you're saying here.
it seems so.
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-19 21:15, Hans-Christoph Steiner wrote:
On Oct 19, 2011, at 3:15 PM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-19 21:07, Hans-Christoph Steiner wrote:
I don't really understand what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-19 18:33, Hans-Christoph Steiner wrote:
Does it work for you?
it seems to work ok. at least the objects are loading (though i get a
lot of tcl/tk errors with some of the examples, but i guess that's
unrelated to the main problem)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-24 22:10, Marvin Humphrey wrote:
I propose we use the suffix -regressiontest.pd for tests, then we can
have a script that crawls the whole pure-data SVN and runs the tests in
place with the libraries they are part of. (-test.pd is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-26 19:29, katja wrote:
Hello,
Here is a .zip with an improved method for unit-testing of signal
before the list gets flooded with updates of updates of zip archives
with the current installment of the unit-testing framework, how about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-30 22:41, Hans-Christoph Steiner wrote:
Having the name SHARED_SOURCE singular highlights that its a single file,
which I think it should be. But since its an internal variable, I would be
OK with it having a different name.
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-30 20:03, Roman Haefeli wrote:
Building iemnet on the Windows build machine still failed:
http://autobuild.puredata.info/auto-build/2011-10-30/logs/2011-10-30_03.31.00_mingw32_nt-5.1_windowsxp-i386_pd-extended.txt
seems like the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-31 15:39, Hans-Christoph Steiner wrote:
On Oct 31, 2011, at 4:59 AM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-30 20:03, Roman Haefeli wrote:
Building iemnet on the Windows build machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-31 15:35, Hans-Christoph Steiner wrote:
You should create some code that solves your issue in your library. Then
we'll take it from there.
hmm, the diff i posted was a cleaned up diff taken from
iem/iemnet/Makefile.
the code is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 03:57, Hans-Christoph Steiner wrote:
Wow, that effects.zip patch is simple yet quite nice. I had some fun with
that.
One possibility for using combinations of Gem, PDP, and Gridflow together is
to use Syphon. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
while i have access to the w32 build machine in the PdLab i have a hard
time getting anything useful to compile.
this is mainly, because i cannot access the binaries built by the
pd-extended autobuild, and i don't want build the whole shebang myself.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 14:43, Hans-Christoph Steiner wrote:
I assume you need access to the binaries for the linking. You can point your
PD_PATH to /home/pd/auto-build/pd-extended/pd and as long as last night's
build succeeded in building the core of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks.
i guess this will only become active after the next autobuild run, correct?
for now, i still have:
$ ls -lha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 16:59, Hans-Christoph Steiner wrote:
On Nov 2, 2011, at 11:58 AM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 22:07, Hans-Christoph Steiner wrote:
Ah, ok, I think I fixed that. I forgot that the msys home tree is separate
from the rest.
seems to work ok,
thanks for the fix.
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ola!
since i don't know any better place to ask, i'll ask here...
debian-testing-amd64.pdlab.hfbk.net
- ---
for whatever reasons, this machine has /tmp (where jenkins creates the
workspaces) mounted as tmpfs (that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-08 11:32, IOhannes m zmoelnig wrote:
chaos.medien.uni-weimar.de
--
i seem to have great troubles to get the OSX10.6
(chaos.medien.uni-weimar.de) machine build a build without fink.
mainly because autoreconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 16:26, Hans-Christoph Steiner wrote:
Even better would be to fix the new build system. One of the reasons I
removed extra/ from Pd-extended and made it a separate library is because of
the brokenness of the build system.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 17:57, Hans-Christoph Steiner wrote:
That is 'make install' doing that, not 'make'. 'make install' is only
supposed to install the files, not generate them.
indeed.
make generated the .d_fat files, and make install copied them to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 18:21, Hans-Christoph Steiner wrote:
On Nov 10, 2011, at 12:16 PM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 17:57, Hans-Christoph Steiner wrote:
That is 'make install' doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 02:07, Ricardo Fabbri wrote:
Hi,
would there be a straightforward way to adjust the hardware color
balance of a webcam through GEM? Do you have experience in
getting/setting those attributes with the PS3 eye webcam which has
been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 09:25, Ricardo Fabbri wrote:
thanks.
ps: you referred to [1] but I see no link.
doh,
[1] http://bear24rw.blogspot.com/2009/11/ps3-eye-driver-patch.html
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 18:44, Hans-Christoph Steiner wrote:
Woo hoo! 32-bit ints in Pd! Well done, thanks for your hard work on this :).
32bit ints?
more like 52bit ints.
fgmadr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-08 18:13, Hans-Christoph Steiner wrote:
jenk...@macosx105-i386.puredata.info
it seems jenkins is still sending with this identity.
could you change that to jenk...@macosx105-i386.pdlab.puredata.info
I like the name standard that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-29 18:29, katja wrote:
On Tue, Nov 29, 2011 at 5:37 PM, Hans-Christoph Steiner h...@at.or.at wrote:
The new build system doesn't need the makefile.dependencies, and that
has always been a bit of a mystery.
Ah, so I'm not the only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i think there are 2 use cases for multi threading.
#1 access a single instance of (lib)pd from multiple threads
#2 allow multiple instances of (lib)pd to co-exist in global memory.
right now, only #1 is possible at all and it takes some effort on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-16 01:15, Hans-Christoph Steiner wrote:
include/Base/
These are the Gem headers, they should be in the 'gem' package, but I
DoH! i wa absolutely convinced that i got that right for the 0.93.3
package. i even closed the relevant debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-16 09:52, IOhannes m zmoelnig wrote:
On 2012-01-16 01:15, Hans-Christoph Steiner wrote:
include/Base/
These are the Gem headers, they should be in the 'gem' package, but I
DoH! i wa absolutely convinced that i got that right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-19 04:28, Hans-Christoph Steiner wrote:
Has anyone tried this? It seems like it would be very valuable for Pd
applications, since Motion JPEG is the standard codec:
http://libjpeg-turbo.virtualgl.org/
libjpeg-turbo is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-19 07:09, Peter Brinkmann wrote:
On 2012-01-14 22:04, Miller Puckette wrote:
To do this I'd replace all globals like
what is wrong with eliminating all directly accessible globals from the
API (like pd_objectmaker) and provide accessor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-29 22:15, SourceForge.net wrote:
I use Ubuntu 64 bit on a pc with intel i7. Until yesterday Ubuntu 10.10 +
Puredata + Gem worked well.
Today i upgrade Ubuntu to 11.4 and 11.11. When i open Puredata, it say:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 00:52, Hans-Christoph Steiner wrote:
That does make more sense, so something like [bytes2utf8], etc.
utf8 is always a list of bytes.
if you get values 255 than it is not utf-8; do you mean unicode points?
fgmasdr
IOhannes
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 15:41, Martin Peach wrote:
On 2012-01-31 03:41, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 00:52, Hans-Christoph Steiner wrote:
That does make more sense, so something like [bytes2utf8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-08 00:36, Mathieu Bouchard wrote:
I mean that this context could be accessed directly if there's no reason
to use accessors. But if locking has to be done before and after
accessing (some of) those members, then it's nice to have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it seems like on the debian-stable-amd64 host of the build-farm, the
Pd-headers have been uninstalled.
at least, Gem build#71 (2011-12-22 10:00:51) succeeded, whereas the next
build#527 (2012-02-19 22:01:47) failed, because out of a sudden it
cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 13:03, IOhannes m zmoelnig wrote:
- `pkg-config --cflags pdextended` returns -I/usr/local/include/pd,
which does not exist at all.
- `pkg-config --cflags pd` fails as well as `pkg-config --cflags puredata`
which also leads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:15, Hans-Christoph Steiner wrote:
- - should /usr/include/m_pd.h be handled likewise, using
update-alternatives? again, i'm not sure whether this is good style and
cannot find such a thing on my system
Pd-extended's headers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:20, Hans-Christoph Steiner wrote:
I reinstalled 'puredata' on debian-stable-amd64, sorry about that, I don't
know what happened there. The build systems are mean to have the Pd-vanilla
headers installed.
thanks.
I'm happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:40, Hans-Christoph Steiner wrote:
Pd-vanilla does provide the sources, but there are two issues:
- it does not include the include/pd/ subdir for headers
i don't think this is an issue.
externals have traditionally included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i move that to the list, as it makes discussion easier.
On 2012-02-27 15:32, SourceForge.net wrote:
Comment By: Hans-Christoph Steiner (eighthave)
idea to change to loglevel+4 to loglevel+3. Either leave verbose()'s
custom level numbering the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-28 16:03, Hans-Christoph Steiner wrote:
Yes, I object. Like I said in the bug tracker and this thread, I think
the offset should either remain the same or be the same as the rest.
may i ask why? what makes 4 better than 3?
fgmasdr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-29 10:52, Cyrille Henry wrote:
Le 29/02/2012 09:34, IOhannes m zmoelnig a écrit :
and both [pix_texture] and [pix_snap] allow for asynchronous
DMA-transfers already (though i only added PBO-tarnsfers to [pix_snap] a
week ago or so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-03-06 17:46, Mathieu Bouchard wrote:
I just wrote a comment in « [grid] not working in pd-extended 0.43.1 »
and it didn't go through to the pd-dev list. I'm wondering what the
selection process is, for routing those comments to pd-dev.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-04-05 20:10, Hans-Christoph Steiner wrote:
Thanks to Greg Pond, we now have a macosx104-powerpc box online and running
builds via jenkins and the Pd-extended auto-build script. The whole Fink
setup is still building, so that's not in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-03 22:30, s p wrote:
That's a very good point, ... it's a good idea to specify GUI
infos, for better interoperability, but it should be explicitly
said that this is optional information
gui information (e.g. spatial layout) is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-13 01:41, Tedb0t wrote:
Hi all,
I just completed building pd-extended on an ARM system. I had to
fix a bunch of dependencies, but I eventually got it all the way
through. (It ended with linux_make install succeeded!) After
that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please always reply on-list!
On 2012-06-13 18:27, Tedb0t wrote:
Sorry?this is my question:
After make install, should pd-extended exist in /usr/bin or
usr/local/bin?
Mine did not.
what? /usr/bin? /usr/local/bin? both? none?
looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 15:19, Thomas Grill wrote:
Hi all, when trying to trace a bug in one of my externals i came
across what could be an issue in the PD API.
The header m_pd.h exposes the function open_via_path which can be
used in externals to search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 15:40, IOhannes m zmoelnig wrote:
Pd-0.43 introduced sys_close() in order to have the same CRT
implementation open and close the file.
prior version of Pd lack this function and therefore there a number
of file-handle leakage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 23:11, Miller Puckette wrote:
Hi all,
Pd version 0.43-3 is available on
http://crca.ucsd.edu/~msp/software.htm
cool.
I'm ready to start hacking on 0.44. The most urgent thing seems to
be for me to go back and work on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-04 21:12, Miller Puckette wrote:
Also... I think OSS/MIDI is the only API now that lets you spit out
arbitrary byes over the MIDI line -- all the others 'protect' you.
i'm not saying that i want to remove OSS-MIDI.
i'm saying that i want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-08 23:39, Hans-Christoph Steiner wrote:
Looks like we'll eventually have to upgrade to the new
SourceForge. Anyone know anything about the new one Allura?
thanks for taking this up (i just wanted to write a similar email).
while i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-18 10:16, Claude Heiland-Allen wrote:
..know if it is possible to use other than 2^n-blocksizes?!
Not for audio connected to a dac~, but for offline stuff it works
(some buggy objects might not cooperate).
You know, I've read about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-24 02:56, Miller Puckette wrote:
I think the most nearly correct thing to do would be to change the
signal structure to add an ?allocated-size field, and put what is
now calcsize in the s_n field of the signal.
m_pd.h
typedef struct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-24 09:24, IOhannes m zmoelnig wrote:
On 2012-10-24 02:56, Miller Puckette wrote:
I'm not 100% sure I can change the size of the signal structure
without breaking binary compatibility with older objects.
i think that t_signal is used
with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlCHqHcACgkQkX2Xpv6ydvTlcwCgmczoV5OY5vBM0+AlF+ReOa2o
LcoAmwcYa6HUxuiU53NonrksunqxseIf
=9IT/
-END PGP SIGNATURE-
From 66e1578b0a9500e754a82f2cc948be6fabb2e6fa Mon Sep 17 00:00:00 2001
From: IOhannes m zmoelnig zmoel...@iem.at
Date: Wed, 24 Oct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-31 04:11, Hans-Christoph Steiner wrote:
I think this would be super valuable. libpd already has an
implementation of parts of this idea, but making fully separate
modules would be quite nice.
Have you talked with Peter Brinkmann at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 18:10, Jonathan Wilkes wrote:
It'd be even better to use a modern GUI toolkit that has simple
tools to implement bleeding edge UX technology from the past 15
years. Stuff like hyperlinks. :)
if hyperlinks is the criterion, then i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 19:05, SourceForge.net wrote:
Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-03 10:05
Message: I tried this and got:
[...]
... is there any way you can supply a patch that doens't add
trailing white space to 1/2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 19:49, Miller Puckette wrote:
Aha... so all the whitespace trouble was their fault, not yours :)
Anyhow, it's on the tracker, but you can get the one I was using:
http://crca.ucsd.edu/~msp/tmp/pa_snapshot_20121031.tgz
but I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-10 22:17, Hans-Christoph Steiner wrote:
I'm CC'ing pd-dev since this is good to have in the public and on
the record.
yes, definitely. thanks.
i'm moving it from pd-list to pd-ev though.
I think the problem was that Fink's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the recent commit 78b81aa3cb90 on the puredata/master branch breaks
ABI compatibility with externals compiled for Pd-0.43.
the problem is that the sys_close() symbol is removed for non-w32
platforms.
therefore all the externals on non-w32 that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-17 10:55, IOhannes m zmoelnig wrote:
this makes packaging externals for e.g. Debian a nightmare, as it
basically should trigger a .so-name change, but since we are
linking against the application instead of an ordinary library, all
401 - 500 of 547 matches
Mail list logo
