|
| | Re: Blockin LNP calls
|
| (...) Yes, the problem is on the host PC (running Red Hat 6.2). What I cant figure out is how identical code works fine if I instantiate the wrapper class in a simple demo app, but once I try calling it form within my CORBA server, it blocks on (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
| | | | Re: Blockin LNP calls
|
| (...) From the statement "data is received by the RCX" I assume you have this problem on the host system. What OS are you using? Also, how does your lnp_logical_write() routine look like? Eddie C. Dost ecd@skynet.be (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
| | | | Re: Blockin LNP calls
|
| (...) ,testaddress, 8); It shouldn't be the real problem, but are you sure about the port paramenter? How about: result = lnp_addressing_write...estbuffer, testlen ,testaddress, testport); Bye, Paolo. --- Maier's Law: If the facts do not conform to (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
| | | | Re: Blockin LNP calls
|
| HELP! I'll ellaborate a little on the details of my previous posting: My code (removing some CORBA detail) looks like this: I have a class "nanOrbDemo_i" which has the following constructor: inline nanOrbDemo_i(){ if ( lnp_init(0,0,0,0,0) ){ cout << (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
| | | | Re: Statically and Dynamically linking lnp ....
|
| (...) Colin, The "standard" for doing this is to wrap the extern "C" { and } in #ifdef __cplusplus clauses. You can see how to do this in most .h files in the include directory. Especially if it's a .h that may be used in mixed (C/C++) projects. (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
| |