Has anyone managed to do it successfully?
I managed to build flext, but when I call the ../flext/build.sh script from within the pyext source dir it fails with the first error being to the fact m_pd.h is not found. I have pd-extended installed and thus m_pd.h lives in /usr/include/pdextended/ and this seems some trivial path problem, but I really can't seem to find a simple way to add that dir to the build process (build.sh seems to call another script but I can't figure out how everything works out).
Somewhat related to this, would it be possible to make py/pyext somewhat more "python-minor-version-agnostic"? Sorry if the question seems naive, I guess the build process actually links to the exact Python in the user's system. In general IMHO it would *really* be nice to be able to have an easy way to hack up externals in python (I could do with even message-only ones) 'by default' with a Pd-extended.
Thanks, Lorenzo.
On 2010-12-07 11:14, Lorenzo Sutton wrote:
Has anyone managed to do it successfully?
I managed to build flext, but when I call the ../flext/build.sh script from within the pyext source dir it fails with the first error being to the fact m_pd.h is not found. I have pd-extended installed and thus m_pd.h lives in /usr/include/pdextended/ and this seems some trivial path problem, but I
try something like adding
<snip> INCPATH+=/usr/include/pdextended </snip> to your config.txt
fgmadft IOhannes
IOhannes m zmoelnig wrote:
On 2010-12-07 11:14, Lorenzo Sutton wrote:
Has anyone managed to do it successfully?
I managed to build flext, but when I call the ../flext/build.sh script from within the pyext source dir it fails with the first error being to the fact m_pd.h is not found. I have pd-extended installed and thus m_pd.h lives in /usr/include/pdextended/ and this seems some trivial path problem, but I
try something like adding
<snip> INCPATH+=/usr/include/pdextended </snip> to your config.txt
I tried, and I actually also spotted in file called buildsys/config-lnx-pd-gcc.txt under the flext directory
<snip> PDPATH=/usr/local/src/pd </snip>
which I changed to
<snip> PDPATH=/usr/include/pdextended </snip>
the build still complains about m_pd.h missing. :/
Lorenzo
fgmadft IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hey Lorenzo, I know I'm not answering exactly to your question but from Thomas grill's site you can find a py.pd_linux binary build with python 2.6: http://grrrr.org/ext/beta/linux/pd/py.pd_linux
I hope it helps you husk
On Tue, Dec 7, 2010 at 11:14 AM, Lorenzo Sutton lsutton@libero.it wrote:
Has anyone managed to do it successfully?
I managed to build flext, but when I call the ../flext/build.sh script from within the pyext source dir it fails with the first error being to the fact m_pd.h is not found. I have pd-extended installed and thus m_pd.h lives in /usr/include/pdextended/ and this seems some trivial path problem, but I really can't seem to find a simple way to add that dir to the build process (build.sh seems to call another script but I can't figure out how everything works out).
Somewhat related to this, would it be possible to make py/pyext somewhat more "python-minor-version-agnostic"? Sorry if the question seems naive, I guess the build process actually links to the exact Python in the user's system. In general IMHO it would *really* be nice to be able to have an easy way to hack up externals in python (I could do with even message-only ones) 'by default' with a Pd-extended.
Thanks, Lorenzo.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Husk 00 -
IOhannes m zmoelnig -
Lorenzo Sutton