[PD] py/pyext missing in pd-extended

[Carlos Pita]

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 at 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 at 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 at 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 at 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