 | | 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 << (...) (26 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. (...) (26 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Blockin LNP calls
|
|
Hi Can anyone tell me why a call to lnp_addressing_write(...) might block? My environment seems okay. I have some simple clients written that have no difficulty in communicating wth the RCX, but I have one client ( a lot more complex) which seems to (...) (26 years ago, 26-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Statically and Dynamically linking lnp ....
|
|
Regarding the previous posting: Please disregard ... I figured it out, but thought it may be useful to post a reply to myself, in case it's ever of use to anyone else using the same tools: I forgot to wrap my include in an ' extern "C" ' block. As I (...) (26 years ago, 26-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Statically and Dynamically linking lnp ....
|
|
Hi All, I was wondering if someone could give me a quick guide as to the compilation/linking options when using liblnp.h etc. I'm having a few difficulties. I wanted to know how exactly to link in the shared library. I tried installing it in the (...) (26 years ago, 26-Aug-00, to lugnet.robotics.rcx.legos)
|
