 | | 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)
|
| |
| | 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 (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC 2.2 r1 released
|
|
Dave, I just wanted to say a BIG THANKS for all your hard work and continued efforts with NQC. Some people debate whether they should stick with NQC or move to Lego's new format. After reading the updated Programmer's guide I know which one I'm (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.2 r1 released
|
|
Ok. Linux builds (i386 and src RPMs, tar.gz) now at (URL). I still need to work on the man page and docs. I'm probably going to start using one of the compile farms to make versions for other architectures and packaging systems. After I do the (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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 (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.legos)
|
