Hi all!
Is py/pyext supposed to be included in pd-extended distribution? I have downloaded and installed both a snapshot of 39.2 and the stable 38.4 but, although they include the examples and documentation of py external, neither of them includes py.pd_linux. See:
tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py.pd_linux and failed tried /site/install/bin/py/py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/py/py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py/py.pd_linux and failed tried /site/install/bin/py/py.pd and failed tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/py/py.pd and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py/py.pd and failed py: can't load library
or:
memeplex:/site/install/bin$ find ../Pd-0.38.4-extended/ -name '*py*' ../Pd-0.38.4-extended/lib/pd/doc/5.reference/maxlib/arraycopy-help.pd ../Pd-0.38.4-extended/lib/pd/doc/5.reference/unauthorized/blm/be_happy.blm ../Pd-0.38.4-extended/lib/pd/doc/5.reference/vasp/vasp_ccopy.pd ../Pd-0.38.4-extended/lib/pd/doc/5.reference/vasp/vasp_copy.pd ../Pd-0.38.4-extended/lib/pd/doc/examples/pmpd/06_pyramide3D.pd ../Pd-0.38.4-extended/lib/pd/doc/examples/py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/buffer.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/pak.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/script.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/sendrecv.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/sig.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/simple.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/tcltk.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/threads.py ../Pd-0.38.4-extended/lib/pd/doc/manuals/py ../Pd-0.38.4-extended/lib/pd/extra/arraycopy.pd_linux ../Pd-0.38.4-extended/lib/pd/extra/maxlib/arraycopy.pd_linux memeplex:/site/install/bin$
Thank you in advance. Regards, Carlos
__________________________________________________ Preguntá. Respondé. DescubrÃ. Todo lo que querÃas saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
Its included in the Pd-extended release versions on Windows and Mac
OS X. Its not part of the auto-builds yet. Its just a matter of
someone doing the work. Any volunteers?D
.hc
On Sep 19, 2006, at 3:55 AM, Carlos Pita wrote:
Hi all!
Is py/pyext supposed to be included in pd-extended distribution? I have downloaded and installed both a snapshot of 39.2 and the stable 38.4 but, although they include the examples and documentation of py external, neither of them includes py.pd_linux. See:
tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/ py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py.pd_linux and failed tried /site/install/bin/py/py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/py/ py.pd_linux and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py/py.pd_linux and failed tried /site/install/bin/py/py.pd and failed tried /site/install/Pd-0.39.2-extended/lib/pd/doc/examples/py/scripts/py/ py.pd and failed tried /site/install/Pd-0.39.2-extended/lib/pd/extra/py/py.pd and failed py: can't load library
or:
memeplex:/site/install/bin$ find ../Pd-0.38.4-extended/ -name '*py*' ../Pd-0.38.4-extended/lib/pd/doc/5.reference/maxlib/arraycopy-help.pd ../Pd-0.38.4-extended/lib/pd/doc/5.reference/unauthorized/blm/ be_happy.blm ../Pd-0.38.4-extended/lib/pd/doc/5.reference/vasp/vasp_ccopy.pd ../Pd-0.38.4-extended/lib/pd/doc/5.reference/vasp/vasp_copy.pd ../Pd-0.38.4-extended/lib/pd/doc/examples/pmpd/06_pyramide3D.pd ../Pd-0.38.4-extended/lib/pd/doc/examples/py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/buffer.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/pak.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/script.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/sendrecv.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/sig.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/simple.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/tcltk.py ../Pd-0.38.4-extended/lib/pd/doc/examples/py/scripts/threads.py ../Pd-0.38.4-extended/lib/pd/doc/manuals/py ../Pd-0.38.4-extended/lib/pd/extra/arraycopy.pd_linux ../Pd-0.38.4-extended/lib/pd/extra/maxlib/arraycopy.pd_linux memeplex:/site/install/bin$
Thank you in advance. Regards, Carlos
__________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
News is what people want to keep hidden and everything else is
publicity. - Bill Moyers
On Tue, 2006-09-19 at 16:32 -0400, Hans-Christoph Steiner wrote:
Its included in the Pd-extended release versions on Windows and Mac
OS X. Its not part of the auto-builds yet. Its just a matter of
someone doing the work. Any volunteers?D
what's the problem of using thomas's binary releases?
t
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Most of the trouble in this world has been caused by folks who can't mind their own business, because they have no business of their own to mind, any more than a smallpox virus has. William S. Burroughs
On Sep 19, 2006, at 6:06 PM, Tim Blechmann wrote:
On Tue, 2006-09-19 at 16:32 -0400, Hans-Christoph Steiner wrote:
Its included in the Pd-extended release versions on Windows and Mac OS X. Its not part of the auto-builds yet. Its just a matter of someone doing the work. Any volunteers?D
what's the problem of using thomas's binary releases?
They don't work with the auto-builds, for one. I would like to
automate the process as much as possible. Gem is now included in the
auto-builds for GNU/Linux and Mac OS X.
Also, one thing that is largely in place is the ability to compile
the whole Pd-extended package for specific CPUs. It would be nice to
include the flext-based stuff. Compiling for the G4 and G5 actually
makes quite a big difference.
.hc
I have the audacity to believe that peoples everywhere can have three
meals a day for their bodies, education and culture for their minds,
and dignity, equality and freedom for their spirits. - Martin
Luther King, Jr.
what's the problem of using thomas's binary releases?
They don't work with the auto-builds, for one.
do you know, what's the reason for that? afaik pd/external binaries should be binary compatible
I would like to
automate the process as much as possible.
you could automate wget :)
tim
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Relying on the government to protect your privacy is like asking a peeping tom to install your window blinds. John Perry Barlow
On Sep 20, 2006, at 9:56 AM, Tim Blechmann wrote:
what's the problem of using thomas's binary releases?
They don't work with the auto-builds, for one.
do you know, what's the reason for that? afaik pd/external binaries should be binary compatible
The binaries work, what I meant was that they don't automatically
build as part of the auto-builds.
I would like to automate the process as much as possible.
you could automate wget :)
Why waste time on kludges? The real thing would be much more useful:
building from source automatically. Its working for basically
everything else right now. It means that we can have a single
package where we can work out the bugs. Bugs can also happen in the
build process.
.hc
They don't work with the auto-builds, for one.
do you know, what's the reason for that? afaik pd/external binaries should be binary compatible
The binaries work, what I meant was that they don't automatically
build as part of the auto-builds.
i see...
I would like to automate the process as much as possible.
you could automate wget :)
Why waste time on kludges?
because no emails with the subject 'py/pyext missing in pd-extended' would be posted to the pd-list?
The real thing would be much more useful:
building from source automatically. Its working for basically
everything else right now. It means that we can have a single
package where we can work out the bugs. Bugs can also happen in the
build process.
sure .. but for now the choice is:
- use wget and include flext externals
- leave it the way it is and don't include wget
of course you could also try to support thomas's build system ... but it seems, there's no one, who's interested in doing the work...
tim
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww! Jack Kerouac
Hi all,
of course you could also try to support thomas's build system ... but it seems, there's no one, who's interested in doing the work...
compiling flext and flext-based externals is pretty straightforward. One could just ignore the flext build system, building flext as a shared or static library (with the first option preferred), and based on that compile the externals. For preprocessor definitions just FLEXT_SYS=2 and FLEXT_SHARED (in the case of a shared library) have to be defined, although some more are optional.
greetings, Thomas
On Sep 20, 2006, at 6:39 PM, Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's build system ...
but it seems, there's no one, who's interested in doing the work...compiling flext and flext-based externals is pretty
straightforward. One could just ignore the flext build system,
building flext as a shared or static library (with the first option
preferred), and based on that compile the externals. For
preprocessor definitions just FLEXT_SYS=2 and FLEXT_SHARED (in the
case of a shared library) have to be defined, although some more
are optional.
I assume this would be using g++. Are flext files all .cc and .cpp?
.hc
Hans-Christoph Steiner schrieb:
On Sep 20, 2006, at 6:39 PM, Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's build system ... but it seems, there's no one, who's interested in doing the work...
compiling flext and flext-based externals is pretty straightforward. One could just ignore the flext build system, building flext as a shared or static library (with the first option preferred), and based on that compile the externals. For preprocessor definitions just FLEXT_SYS=2 and FLEXT_SHARED (in the case of a shared library) have to be defined, although some more are optional.
I assume this would be using g++. Are flext files all .cc and .cpp?
yes, .cpp only.
greetings, Thomas
Hi all!
I'm not able to build a functional py external from the sources. I have tried (almost all) the combinations obtained along these 4 axes:
pd) cvs / 0.39-2
flext+py) cvs / 0.5.0+0.2.0
py build kind) build-release-single / build-release-multi
python) 2.3.? (can't remember) / 2.4.4
multi builds simply kill off pd during startup. The single ones let pd start but then many actions from the py sample patches abort pd execution (while others seem to work fine, I can't detect any pattern here).
Any ideas? I've spent almost an entire day trying to add python support to pd, it's getting very frustrating.
Thank you in advace. Regards, Carlos
--- Thomas Grill gr@grrrr.org escribió:
Hans-Christoph Steiner schrieb:
On Sep 20, 2006, at 6:39 PM, Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's
build system ...
but it seems, there's no one, who's interested in doing
the work...
compiling flext and flext-based externals is
pretty straightforward.
One could just ignore the flext build system,
building flext as a
shared or static library (with the first option
preferred), and based
on that compile the externals. For preprocessor
definitions just
FLEXT_SYS=2 and FLEXT_SHARED (in the case of a
shared library) have
to be defined, although some more are optional.
I assume this would be using g++. Are flext files
all .cc and .cpp? yes, .cpp only.
greetings, Thomas
-- Thomas Grill http://grrrr.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
__________________________________________________ Preguntá. Respondé. DescubrÃ. Todo lo que querÃas saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
Mh, I'm not sure but the following warning could be related to the problem (it's not shown for single py builds). Regards, Carlos
In file included from /usr/include/python2.4/Python.h:8, from source/pyprefix.h:24, from source/main.h:14, from source/pybase.h:14, from source/main.cpp:11: /usr/include/python2.4/pyconfig.h:838:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/pthread.h:18, from /site/install/flext-cvs/include/flext/flext.h:41, from source/pyprefix.h:15, from source/main.h:14, from source/pybase.h:14, from source/main.cpp:11: /usr/include/features.h:150:1: warning: this is the location of the previous definition
-- Carlos Pita carlosjosepita@yahoo.com.ar escribió:
Hi all!
I'm not able to build a functional py external from the sources. I have tried (almost all) the combinations obtained along these 4 axes:
pd) cvs / 0.39-2
flext+py) cvs / 0.5.0+0.2.0
py build kind) build-release-single / build-release-multi
python) 2.3.? (can't remember) / 2.4.4
multi builds simply kill off pd during startup. The single ones let pd start but then many actions from the py sample patches abort pd execution (while others seem to work fine, I can't detect any pattern here).
Any ideas? I've spent almost an entire day trying to add python support to pd, it's getting very frustrating.
Thank you in advace. Regards, Carlos
--- Thomas Grill gr@grrrr.org escribió:
Hans-Christoph Steiner schrieb:
On Sep 20, 2006, at 6:39 PM, Thomas Grill wrote:
Hi all,
of course you could also try to support
thomas's
build system ...
but it seems, there's no one, who's interested in
doing
the work...
compiling flext and flext-based externals is
pretty straightforward.
One could just ignore the flext build system,
building flext as a
shared or static library (with the first option
preferred), and based
on that compile the externals. For preprocessor
definitions just
FLEXT_SYS=2 and FLEXT_SHARED (in the case of a
shared library) have
to be defined, although some more are optional.
I assume this would be using g++. Are flext
files
all .cc and .cpp? yes, .cpp only.
greetings, Thomas
-- Thomas Grill http://grrrr.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
__________________________________________________ Preguntá. Respondé. DescubrÃ. Todo lo que querÃas saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
__________________________________________________ Preguntá. Respondé. DescubrÃ. Todo lo que querÃas saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
Hi Carlos, if i understand correctly py/pyext is building ok (apart from the _POSIX_SOURCE redefinition warning which is harmless) but loading it lets pd crash, right? Which system are you using? Linux?
I would set the positions on the 4 axes to: pd) 0.39-2 flext+py) cvs py build kind) build-debug-multi (for testing, later change to build-release-multi) python) 2.4.3 (is there a 2.4.4 anyway?)
Since i have never heard of such problems i would need more info to be able to help you. If you're under linux, run pd in gdb and send me a backtrace of the crash. With the py/pyext debug version you might not be able to use external Python modules (as they have to be debug builds as well), but basic operation should work.
all the best, Thomas
Am 21.09.2006 um 01:39 schrieb Carlos Pita:
Hi all!
I'm not able to build a functional py external from the sources. I have tried (almost all) the combinations obtained along these 4 axes:
pd) cvs / 0.39-2
flext+py) cvs / 0.5.0+0.2.0
py build kind) build-release-single / build-release-multi
python) 2.3.? (can't remember) / 2.4.4
multi builds simply kill off pd during startup. The single ones let pd start but then many actions from the py sample patches abort pd execution (while others seem to work fine, I can't detect any pattern here).
Any ideas? I've spent almost an entire day trying to add python support to pd, it's getting very frustrating.
Thank you in advace. Regards, Carlos
--- Thomas Grill gr@grrrr.org escribió:
Hans-Christoph Steiner schrieb:
On Sep 20, 2006, at 6:39 PM, Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's
build system ...
but it seems, there's no one, who's interested in doing
the work...
compiling flext and flext-based externals is
pretty straightforward.
One could just ignore the flext build system,
building flext as a
shared or static library (with the first option
preferred), and based
on that compile the externals. For preprocessor
definitions just
FLEXT_SYS=2 and FLEXT_SHARED (in the case of a
shared library) have
to be defined, although some more are optional.
I assume this would be using g++. Are flext files
all .cc and .cpp? yes, .cpp only.
greetings, Thomas
-- Thomas Grill http://grrrr.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
__________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
hi there, i think i had the same problems as Carlos on linux (xubuntu dapper). i had to comment out compile options in order for pyext no to crash pd at startup. it was also quite difficult for me to find it out. what are those flags good for by the way?
# UFLAGS=-msse -mfpmath=sse -ffast-math # OFLAGS+=-march=pentium4
i did not understand why we would need wget in order to automatize the pyext build in pd-extended?
i can see that building flext and py/pyext for all platforms automatically can be a bit of a headache because there are many steps but they are very logically ordered.
vincent
Hi all,
i think i had the same problems as Carlos on linux (xubuntu dapper). i had to comment out compile options in order for pyext no to crash pd at startup. it was also quite difficult for me to find it out. what are those flags good for by the way?
# UFLAGS=-msse -mfpmath=sse -ffast-math # OFLAGS+=-march=pentium4
ah, i remember... you are using an AMD cpu, right? I think there was a problem with SSE, which is more a gcc or cpu bug than a flext bug. The flags are normally good for some speedup, but it's a good idea to comment them out for testing purposes. Carlos, is your machine also AMD-based?
i did not understand why we would need wget in order to automatize the pyext build in pd-extended?
i can see that building flext and py/pyext for all platforms automatically can be a bit of a headache because there are many steps but they are very logically ordered.
it's one step for the flext library and one step for each additional flext-based external. Not really a complication....
greetings, Thomas
On Thu, 21 Sep 2006, Thomas Grill wrote:
ah, i remember... you are using an AMD cpu, right? I think there was a problem with SSE, which is more a gcc or cpu bug than a flext bug. The flags are normally good for some speedup, but it's a good idea to comment them out for testing purposes. Carlos, is your machine also AMD-based?
Is there any documentation of AMD-specific problems in SSE instructions?
(I've never heard of any of them.)
Is it a AMD CPU problem or an AMD-specific bug in GCC ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
Mathieu Bouchard a écrit :
On Thu, 21 Sep 2006, Thomas Grill wrote:
ah, i remember... you are using an AMD cpu, right?
well i don't think i had this pb only with an AMD cpu - but i must say it happened a while ago and i changed of system meanwhile.
i just tried to compile a fresh pd0.40 on an intel celeron 2.6G with xubuntu dapper. flext with all optimization flags and pyext+numarray from cvs and everything works fine! i used:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data login cvs -z3 -d:pserver:anonymous@pure-data.cvs.sourceforge.net:/cvsroot/pure-data/ co externals/grill
concerning the number of steps:
doing it by hand requires :
1- cd externals/grill/flext 2- bash build.sh pd gcc ignore error message 3- sudo emacs buildsys/config-lnx-pd-gcc.txt 4- PDPATH=/usr/local/pd 5- adapt optimization flags? 6- bash build.sh pd gcc build ignore error message 7- bash build.sh pd gcc build 8- bash build.sh pd gcc install
seven steps for flext
1- bash ../flext/build.sh pd gcc -> ignore error message 2- sudo emacs config.txt 3- PY_NUMARRAY=1 4- bash ../flext/build.sh pd gcc build 5- sudo bash ../flext/build.sh pd gcc install 6- sudo mkdir /usr/local/lib/pd/doc/pyext 7- sudo cp -r pd/* scripts/* /usr/local/lib/pd/doc/pyext/
seven steps for pyext
ok i am slightly exagerating but still i would naturaly guess that reducing all these to two steps automagically is probably a little bit of a headache. but i must admit that i did not look into the autobuil system for pd-extended...
greetings, vincent
I think there was a problem with SSE, which is more a gcc or cpu bug than a flext bug. The flags are normally good for some speedup, but it's a good idea to comment them out for testing purposes. Carlos, is your machine also AMD-based?
Is there any documentation of AMD-specific problems in SSE instructions?
(I've never heard of any of them.)
Is it a AMD CPU problem or an AMD-specific bug in GCC ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hello, i am trying to use hid-0.6 on puredyne but when i load it i get: ELF file data encoding not little-endian
so i had to compile it against the source on /opt/dyne it loads at pd startup now but when i try to use it it seems that no device are present error [hid] open /dev/input/event0 failed
a second related question: how can i include it into puredyne so that it will be present on the cdrom?
vincent
Even better, use [hid] from CVS. There are a lot of improvements
since 0.6 and I just fixed a key bug last night. Turns out it was a
relatively simple pointer bug.
Also, AFAIK, endianness is not an issue with hid/input.h stuff. GNU/ Linux generally handles endianness issues for you.
.hc
On Sep 21, 2006, at 11:27 AM, vincent rioux wrote:
hello, i am trying to use hid-0.6 on puredyne but when i load it i get: ELF file data encoding not little-endian
so i had to compile it against the source on /opt/dyne it loads at pd startup now but when i try to use it it seems that no device are present error [hid] open /dev/input/event0 failed
a second related question: how can i include it into puredyne so that it will be present on
the cdrom?vincent
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore
Hey all,
So I'm starting work on pixelTANGO again and need to get things working in pd-extended. Has there been any changes in this dialogue since I've been out of the loop?
Thomas, if you could provide a simple "normal" makefile for all platforms for flext and flext externals then I can see if I can figure out how to integrate that into the PD extended (pixelTANGO) makefile(s).
I'm not gcc expert, so a set of sample makefiles would be ideal.
If anyone else has started the work please drop me a line so we can coordinate.
Thanks all,
B. Bogart
Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's build system ... but it seems, there's no one, who's interested in doing the work...
compiling flext and flext-based externals is pretty straightforward. One could just ignore the flext build system, building flext as a shared or static library (with the first option preferred), and based on that compile the externals. For preprocessor definitions just FLEXT_SYS=2 and FLEXT_SHARED (in the case of a shared library) have to be defined, although some more are optional.
greetings, Thomas
The Pd-extended release just includes THomas's binaries for all the
flext stuff. It would definitely be nicer if that was all built from
source and included.
Since you'll be working on a lot of GUI stuff, I'd be very interested
to hear how the new GUI stuff works out in Pd-extended.
.hc
On May 31, 2007, at 4:23 PM, B. Bogart wrote:
Hey all,
So I'm starting work on pixelTANGO again and need to get things
working in pd-extended. Has there been any changes in this dialogue since I've been out of the loop?Thomas, if you could provide a simple "normal" makefile for all platforms for flext and flext externals then I can see if I can figure out how to integrate that into the PD extended (pixelTANGO) makefile (s).
I'm not gcc expert, so a set of sample makefiles would be ideal.
If anyone else has started the work please drop me a line so we can coordinate.
Thanks all,
B. Bogart
Thomas Grill wrote:
Hi all,
of course you could also try to support thomas's build system ...
but it seems, there's no one, who's interested in doing the work...compiling flext and flext-based externals is pretty
straightforward. One could just ignore the flext build system, building flext as a
shared or static library (with the first option preferred), and based on that compile the externals. For preprocessor definitions just
FLEXT_SYS=2 and FLEXT_SHARED (in the case of a shared library) have to be defined, although some more are optional.greetings, Thomas
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours; and
this we should do freely and generously. - Benjamin Franklin
Tim Blechmann a écrit :
On Tue, 2006-09-19 at 16:32 -0400, Hans-Christoph Steiner wrote:
Its included in the Pd-extended release versions on Windows and Mac
OS X. Its not part of the auto-builds yet. Its just a matter of
someone doing the work. Any volunteers?Dwhat's the problem of using thomas's binary releases?
hi tim, what i can remember is that there is a slight difference in syntax (arguments of the ._send method) between the official binaries that thomas put on his site and the latest "beta" version which is also on cvs - this makes it a bit tricky to use one's pyext code on different platforms with pd-extended or not. moreover i think pyext in pd-extended on osx just crashes.
thomas, i have been using the beta version for quite some time now and it seems to be pretty ok. are you waiting for something precise before releasing it as a versioned one?
best, vincent
t
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Most of the trouble in this world has been caused by folks who can't mind their own business, because they have no business of their own to mind, any more than a smallpox virus has. William S. Burroughs
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
thomas, i have been using the beta version for quite some time now and it seems to be pretty ok. are you waiting for something precise before releasing it as a versioned one?
yes, for some free time to come. It's not exactly at the top of my prioritized todo queue.
greetings, Thomas
-
B. Bogart -
Carlos Pita -
Hans-Christoph Steiner -
Mathieu Bouchard -
Thomas Grill -
Tim Blechmann -
vincent rioux