Hi!
I've got sources and a compiled DLL for OSC support on Windows. This version is rather old (20020416) and I wanted to update it from the CVS repository. I determined that the CVS version (v1.4) don't compile on my system - there are some errors I can't explain with my rather poor knowledge of the pd API. I've seen that most changes were done for Apple platform. My version works on Windows 2000 3 years without any problems (I've done some bug fixes).
Does it make sense to merge my version to the CVS version, or adapt the CVS to be Windows-compliant? If yes, can somebody do it or advise me? I can do all compilations on Windows and do extensive tests of the merged version on Windows 2000.
br, Peter
Hallo, Piotr Majdak hat gesagt: // Piotr Majdak wrote:
I've got sources and a compiled DLL for OSC support on Windows. This version is rather old (20020416) and I wanted to update it from the CVS repository. I determined that the CVS version (v1.4) don't compile on my system - there are some errors I can't explain with my rather poor knowledge of the pd API. I've seen that most changes were done for Apple platform. My version works on Windows 2000 3 years without any problems (I've done some bug fixes).
Could you give some more details? Like what error messages are there, what compiler are you using, etc?
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "plak" @ http://footils.org/cms/show/44
Hi!
Frank Barknecht wrote:
Could you give some more details? Like what error messages are there, what compiler are you using, etc?
The Build errors are:
--------------------Configuration: OSC - Win32 Debug-------------------- Compiling... dumpOSC.c d:\temp\myosc\dumposc.c(80) : warning C4273: 'sys_addpollfn' : inconsistent dll linkage. dllexport assumed. d:\temp\myosc\dumposc.c(328) : error C2054: expected '(' to follow 'OSC_API' d:\temp\myosc\dumposc.c(332) : error C2085: 'dumpOSC_setup' : not in formal parameter list d:\temp\myosc\dumposc.c(332) : error C2143: syntax error : missing ';' before '{' d:\temp\myosc\dumposc.c(516) : error C2065: 'int32_t' : undeclared identifier d:\temp\myosc\dumposc.c(516) : error C2059: syntax error : ')' d:\temp\myosc\dumposc.c(517) : error C2059: syntax error : ')' d:\temp\myosc\dumposc.c(522) : error C2059: syntax error : ')' d:\temp\myosc\dumposc.c(525) : error C2061: syntax error : identifier 'ReadTime' d:\temp\myosc\dumposc.c(525) : error C2059: syntax error : ';' d:\temp\myosc\dumposc.c(525) : error C2059: syntax error : 'type' d:\temp\myosc\dumposc.c(566) : error C2059: syntax error : ')' d:\temp\myosc\dumposc.c(567) : error C2059: syntax error : ')' d:\temp\myosc\dumposc.c(570) : error C2061: syntax error : identifier 'dumpOSC_SendReply' d:\temp\myosc\dumposc.c(570) : error C2059: syntax error : ';' d:\temp\myosc\dumposc.c(570) : error C2059: syntax error : 'type' OSCroute.c d:\temp\myosc\oscroute.c(129) : error C2054: expected '(' to follow 'OSC_API' d:\temp\myosc\oscroute.c(129) : error C2085: 'OSCroute_setup' : not in formal parameter list d:\temp\myosc\oscroute.c(129) : error C2143: syntax error : missing ';' before '{' sendOSC.c d:\temp\myosc\sendosc.c(476) : warning C4013: 'fgets' undefined; assuming extern returning int d:\temp\myosc\sendosc.c(476) : error C2065: 'stdin' : undeclared identifier d:\temp\myosc\sendosc.c(476) : warning C4047: '!=' : 'int ' differs in levels of indirection from 'void *' d:\temp\myosc\sendosc.c(562) : warning C4013: 'sscanf' undefined; assuming extern returning int d:\temp\myosc\sendosc.c(839) : warning C4013: 'vfprintf' undefined; assuming extern returning int d:\temp\myosc\sendosc.c(839) : error C2065: 'stderr' : undeclared identifier Error executing cl.exe.
OSC.dll - 20 error(s), 5 warning(s)
I use MS VC++6 on Windows2000. The most syntax errors are a consequence of the unknown int32_t data type.
Another problem is, that routeOSC became OSCroute and changed completly. I'm just checking the diffs to my version and will see what I can do with that...
Thanks for any support...
br, Peter
Piotr Majdak wrote:
Hi!
Frank Barknecht wrote:
Could you give some more details? Like what error messages are there, what compiler are you using, etc?
Just one error left: conversion from unsigned __int64 to double not implemented, use signed __int64.
Do you have (double)(unsigned __int64) on your platform implemented? (I'm not sure what the last editor of this code did...)
br, Peter
Piotr Majdak wrote:
Just one error left: conversion from unsigned __int64 to double not implemented, use signed __int64.
Do you have (double)(unsigned __int64) on your platform implemented? (I'm not sure what the last editor of this code did...)
Forget this question: conversion from __int64 to double is lossy, no matter if signed or unsigned.
So the question is: who needs dumpOSC_SendReply() in OSC? I'm going to comment this part of dumpOSC...
br, Peter
Do you have (double)(unsigned __int64) on your platform implemented? (I'm not sure what the last editor of this code did...)
So the question is: who needs dumpOSC_SendReply() in OSC? I'm going to comment this part of dumpOSC...
hmm. has anyone thought about making a liblo-based OSC external, instead of investing any more effort in the circa-1996 OSCx? i mean besides the fact that its full of bugs and missing features its incredibly "dumb" and cant even work with modern apps that choose random ports to connect from and instantiate a 2-way connection etc..i had to bug the author of another app just to make a special feature so that i could connect to it from PD, for example..
carmen
br, Peter
hmm. has anyone thought about making a liblo-based OSC external
Yes, i have. I have already ported liblo to Windows - it needs gcc though, won't compile with MSVC. Besides not having enough time now, i'd like to wait for zeroconf support in liblo before i'm really going to start.
all the best, Thomas
carmen wrote:
hmm. has anyone thought about making a liblo-based OSC external, instead of investing any more effort in the circa-1996 OSCx? i mean besides the fact that its full of bugs and missing features its incredibly "dumb" and cant even work with modern apps that choose random ports to connect from and instantiate a 2-way connection etc..i had to bug the author of another app just to make a special feature so that i could connect to it from PD, for example..
From my point of view, the version I use is adequate for me. But, as you mentioned, it's full of bugs and I would appreciate to see an improvement for OSC4pd. Unfortunately I can't help you...
I've managed to compile the OSC from CSV for Windows 2000.
Changes are:
- dumpOSC routes up to 128 branches (tested with 24)
- sendOSC doesn't crash on longer messages (tested with one argument of
120 characters)
- sendOSC # of arguments limited by the length of the message (tested
with 110 messages)
- dumpOSC_SendReply() removed (this implementation was not cross-platform)
This package was tested on Windows 2000 only. I'd like to ask you to try to compile/test it on other systems. (If you need them at all, thanks Thomas we'll get a better implementation.)
As I don't have any CVS client here and I'm not a member of the SF-Project: may I ask someone to check in the files? You'll find the files (zipped to one file) here: http://iem.at/~majdak/download/OSC/OSC4pd_CVS_0.3.zip I kept the structure identical to the repository.
br, Peter
Hallo!
As I don't have any CVS client here and I'm not a member of the SF-Project: may I ask someone to check in the files? You'll find the files (zipped to one file) here: http://iem.at/~majdak/download/OSC/OSC4pd_CVS_0.3.zip I kept the structure identical to the repository.
okay, I'll do it ...
LG Georg
br, Peter
Hallo!
hm ... just a question: Should it replace OSCx or should it be in a seperate folder (because you named it different ...) ?
LG Georg
I kept the structure identical to the repository.
okay, I'll do it ...
LG Georg
br, Peter
Georg Holzmann wrote:
Hallo!
hm ... just a question: Should it replace OSCx or should it be in a seperate folder (because you named it different ...) ?
forget the stupid question ... ;) will check it in ...
LG Georg
Georg Holzmann wrote:
Georg Holzmann wrote:
Hallo!
hm ... just a question: Should it replace OSCx or should it be in a seperate folder (because you named it different ...) ?
forget the stupid question ... ;) will check it in ...
Thanks. By the way: do you know a nice CSV client for windows?
br, Peter
Piotr Majdak wrote:
Thanks. By the way: do you know a nice CSV client for windows?
wincvs ? http://www.wincvs.org/ tortoisecvs ? http://www.tortoisecvs.org/
mfg.nzr..as IOhannes
IOhannes m zmoelnig wrote:
Thanks. By the way: do you know a nice CSV client for windows?
wincvs ? http://www.wincvs.org/ tortoisecvs ? http://www.tortoisecvs.org/
What I forgot: I need a CVS and subversion client. Do you know a GUI for both (for Windows)?
br, Peter
Piotr Majdak wrote:
IOhannes m zmoelnig wrote:
Thanks. By the way: do you know a nice CSV client for windows?
wincvs ? http://www.wincvs.org/ tortoisecvs ? http://www.tortoisecvs.org/
What I forgot: I need a CVS and subversion client. Do you know a GUI for both (for Windows)?
i don't think there is one for both systems.
however, you could use tortoiseSVN and tortoiseCVS and manage both from your explorer (ihave no experience with any svn clients on w32)
btw, i have my information from http://www.google.at/search?q=windows+svn+client
br, Peter
IOhannes m zmoelnig wrote:
btw, i have my information from http://www.google.at/search?q=windows+svn+client
Yeah, i tried that too. 158.000 items and the first 30 tell you that Subversion is a better CVS :-(
however, you could use tortoiseSVN and tortoiseCVS and manage both from your explorer (ihave no experience with any svn clients on w32)
I'll give them a try. Thanks!
br, Peter
Piotr Majdak schrieb:
IOhannes m zmoelnig wrote:
Thanks. By the way: do you know a nice CSV client for windows?
wincvs ? http://www.wincvs.org/ tortoisecvs ? http://www.tortoisecvs.org/
What I forgot: I need a CVS and subversion client. Do you know a GUI for both (for Windows)?
there's also a tortoisesvn that you can use alongside with tortoisecvs. I use it a lot... it's quite ok.
all the best, Thomas
Piotr Majdak wrote:
Hi!
Does it make sense to merge my version to the CVS version, or adapt the CVS to be Windows-compliant?
yes it does make sense and it is very much welcome.
If yes, can somebody do it or advise me? I
since i will not _do_ it, how should i advise you ? (what do you want to know exactly ?)
can do all compilations on Windows and do extensive tests of the merged version on Windows 2000.
that'll be great.
i think the original author of OSCx is not that active any more (or at least: they is not maintaining it actively)
so it is up to the community (you!) to keep the code functional and up-to-date.
btw, a bug has been reported at http://sourceforge.net/tracker/index.php?func=detail&aid=1217922&gro... and i don't know whether it has already been fixed. so while you're at it ;-)
mfg.ads.r IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
i think the original author of OSCx is not that active any more (or at least: they is not maintaining it actively)
AFAIK he once said, that the version of OSC for Pd in CVS should be and is the canonical version, that is, development of OSC happens inside CVS. Because of this I think, it's okay for other developers to fix any "normal" bugs there, if they are open for "long enough" or if they are very grave (like the licensing stuff). At least I did it sometimes in the past and others like Hans also did it.
Regarding fixes in the build system: OSC should build using Guenther's build system as well as using Scons. IMO it is not necessary to put a lot of work into making OSC's own build system work as well. As far as I'm concerned the local build system could be dropped altogether in favour of Scons or Guenther's built. But that is just my view of things.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "plak" @ http://footils.org/cms/show/44
Hi!
IOhannes m zmoelnig wrote:
yes it does make sense and it is very much welcome.
OK.
since i will not _do_ it, how should i advise you ? (what do you want to know exactly ?)
I will have _many_ questions and it would be great to get some nice answers. That's all.
And here we go:
- I use the CVS repository
http://cvs.sourceforge.net/viewcvs.py/pure-data/externals/OSCx/ Is this the latest version?
- do you know what sys_addpollfn is? cc can't find it, what include do I
need?
- what do I need for the int32_t data type?
btw, a bug has been reported at http://sourceforge.net/tracker/index.php?func=detail&aid=1217922&gro... and i don't know whether it has already been fixed. so while you're at it ;-)
yeah, I know that. This bug didn't affect me, but while I'm on it I'll try to find a better solution for the hardcoded length of an argument.
br, Peter
Hallo!
- do you know what sys_addpollfn is? cc can't find it, what include do I
need?
should be something related with timer stuff and should be in m_imp.h (shouldn't it?), but I just looked at m_imp.h and couldn't find it ... have there been some changes ?
I found this with google: http://lists.puredata.info/pipermail/pd-dev/2003-04/001122.html
LG Georg
Georg Holzmann wrote:
Hallo!
- do you know what sys_addpollfn is? cc can't find it, what include do
I need?
should be something related with timer stuff and should be in m_imp.h (shouldn't it?), but I just looked at m_imp.h and couldn't find it ... have there been some changes ?
I found this with google: http://lists.puredata.info/pipermail/pd-dev/2003-04/001122.html
Thanks. I think I don't need that - I' try to exclude the declaration, we'll see if the linker will grumble. (Can't link until now... ;-)
br, PEter
- do you know what sys_addpollfn is? cc can't find it, what include
do I need?
sys_addpollfn is defined in s_stuff.h, that's a private header ... so you are basically not allowed to use this :-) just make sure, that s_stuff.h is in the search paths ...
- what do I need for the int32_t data type?
maybe just add a #define int32_t t_int
cheers ... tim
Tim Blechmann wrote:
- what do I need for the int32_t data type?
maybe just add a #define int32_t t_int
OK?! Compiler likes it... No clue about int32_t and t_int, we'll see if it works...
thanx, Peter
Piotr Majdak wrote:
- do you know what sys_addpollfn is? cc can't find it, what include do
I need?
From my study of the code of pd-0.38-4:
sys_addpollfn(sys_guisock, (t_fdpollfn)socketreceiver_read, sys_socketreceiver) in s_inter.c. This adds socketreceiver_read to the list of functions checked during sys_domicrosleep() typedef struct _fdpoll { int fdp_fd; t_fdpollfn fdp_fn; void *fdp_ptr; } t_fdpoll;
Martin
I would be extremely interested in the results because I would rather urgently like to use OSC with PD on WinXP, but don't have any experience with CVS or compiling C programs or anything like this. Also I got two versions of an osc.dll but don't seem to be able to get them working
Best wishes Urs
Piotr Majdak schrieb:
Hi!
I've got sources and a compiled DLL for OSC support on Windows. This version is rather old (20020416) and I wanted to update it from the CVS repository. I determined that the CVS version (v1.4) don't compile on my system - there are some errors I can't explain with my rather poor knowledge of the pd API. I've seen that most changes were done for Apple platform. My version works on Windows 2000 3 years without any problems (I've done some bug fixes).
Does it make sense to merge my version to the CVS version, or adapt the CVS to be Windows-compliant? If yes, can somebody do it or advise me? I can do all compilations on Windows and do extensive tests of the merged version on Windows 2000.
br, Peter
hi piotr
i think this version is more recent. www.ixi-software.net/content/download/osc.zip
best
Piotr Majdak wrote:
Hi!
I've got sources and a compiled DLL for OSC support on Windows. This version is rather old (20020416) and I wanted to update it from the CVS repository. I determined that the CVS version (v1.4) don't compile on my system - there are some errors I can't explain with my rather poor knowledge of the pd API. I've seen that most changes were done for Apple platform. My version works on Windows 2000 3 years without any problems (I've done some bug fixes).
Does it make sense to merge my version to the CVS version, or adapt the CVS to be Windows-compliant? If yes, can somebody do it or advise me? I can do all compilations on Windows and do extensive tests of the merged version on Windows 2000.
br, Peter
-
altern -
carmen -
Frank Barknecht -
Georg Holzmann -
IOhannes m zmoelnig -
Martin Peach -
Piotr Majdak -
Thomas Grill -
Tim Blechmann -
Urs Liska