[PD-dev] net objects

[cyrille henry]

hello,
this is what i was looking for to control a lanbox dmx controler.
send object work, but i have problem with receive objects :

cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow 
-Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch 
-I../../src -o udpreceive.o -c udpreceive.c
cc1: warnings being treated as errors
udpreceive.c: In function ‘udpreceive_read’:
udpreceive.c:49: attention : pointer targets in passing argument 6 of 
‘recvfrom’ differ in signedness
make: *** [udpreceive.pd_linux] Erreur 1
cc -DPD -O2 -funroll-loops -fomit-frame-pointer -Wall -W -Wshadow 
-Wstrict-prototypes -Werror -Wno-unused -Wno-parentheses -Wno-switch 
-I../../src -o tcpreceive.o -c tcpreceive.c
cc1: warnings being treated as errors
tcpreceive.c: In function ‘tcpreceive_connectpoll’:
tcpreceive.c:196: attention : pointer targets in passing argument 3 of 
‘accept’ differ in signedness
make: *** [tcpreceive.pd_linux] Erreur 1


could this object be found on the cvs?

thanks
Cyrille



Martin Peach a écrit :
> I made some net externals that use raw bytes instead of pd messages:
> http://puredata.info/Members/martinrp/netobjects
> They are based on netreceive and netsend. Maybe they could be 
> incorporated into pd since they're using poll functions which are not 
> officially exposed in m_pd.h.
> I'm working on packOSC and upackOSC which interface to these objects via 
> lists of floats-constrained-to-be-bytes. unpackOSC will allow routing 
> via route instead of OSCroute since the path will be separated into 
> symbols and output as a list. The data will be output as a separate list.
> 
> Martin
> 
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev
> 
>