[PD] py/pyext missing in pd-extended

[Thomas Grill]

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