To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 2839
     
   
Subject: 
Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 6 Sep 2002 15:07:38 GMT
Viewed: 
1894 times
  

Hi all,

I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile. First,
I tried compiling it on its own - no joy (unresolved symbol _main - it
wanted to be part of an MFC project). So I start an MFC project and import
the stub.c file and tell the preprocessor where to find the include. Again,
no joy. I get the error message

CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

TIA

Tim

   
         
     
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 6 Sep 2002 16:31:36 GMT
Viewed: 
1993 times
  

To my knowledge nobody has been succesful with WinLNP!

I gave up after a while and now use LNP under Linux.

There was some work that somboby did which allowed the deamon
to run on Linux but the LNP program could be run under windows.

U could do a search in the mailing list archives.

Hope this helps

PS  If u get WinLNP to work , let every one know how u did it!

----- Original Message -----
From: "Tim Auton" <tim.lugnet@uton.org>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 4:07 PM
Subject: Winliblnp problems


Hi all,

I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile. • First,
I tried compiling it on its own - no joy (unresolved symbol _main - it
wanted to be part of an MFC project). So I start an MFC project and import
the stub.c file and tell the preprocessor where to find the include. • Again,
no joy. I get the error message

CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

TIA

Tim

    
          
      
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 6 Sep 2002 16:47:35 GMT
Viewed: 
2151 times
  

I am using LNP under Linux, I was referring to your suggested solution,
which is both sensibly and confusingly called Winliblnp (distinct from
winlnp) - a port of liblnp for Windows.

I want to write robot control apps using video feedback, and my poor Linux
box doesn't have USB so I've had to venture into the (nightmare) world of
Visual C++.

Tim

"Shehryar Shaheen" <shehryar.shaheen@ul.ie> wrote in message
news:009e01c255c2$dfc82f10$1d96c988@2KDCQ9370JSSHAHEEN...
To my knowledge nobody has been succesful with WinLNP!

I gave up after a while and now use LNP under Linux.

There was some work that somboby did which allowed the deamon
to run on Linux but the LNP program could be run under windows.

U could do a search in the mailing list archives.

Hope this helps

PS  If u get WinLNP to work , let every one know how u did it!

----- Original Message -----
From: "Tim Auton" <tim.lugnet@uton.org>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 4:07 PM
Subject: Winliblnp problems


Hi all,

I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile. • First,
I tried compiling it on its own - no joy (unresolved symbol _main - it
wanted to be part of an MFC project). So I start an MFC project and • import
the stub.c file and tell the preprocessor where to find the include. • Again,
no joy. I get the error message

CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

TIA

Tim


     
           
      
Subject: 
legOS 0.1.7
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Sat, 7 Sep 2002 17:37:24 GMT
Viewed: 
2070 times
  

I need information about this version of legOS !!

please send me :)

nanobapt

    
          
     
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 6 Sep 2002 16:49:50 GMT
Viewed: 
2030 times
  

a ActiveX is easy to written with an other Comm activeX for Windows no ?

nanobapt
----- Original Message -----
From: Shehryar Shaheen <shehryar.shaheen@ul.ie>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 6:31 PM
Subject: Re: Winliblnp problems


To my knowledge nobody has been succesful with WinLNP!

I gave up after a while and now use LNP under Linux.

There was some work that somboby did which allowed the deamon
to run on Linux but the LNP program could be run under windows.

U could do a search in the mailing list archives.

Hope this helps

PS  If u get WinLNP to work , let every one know how u did it!

----- Original Message -----
From: "Tim Auton" <tim.lugnet@uton.org>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 4:07 PM
Subject: Winliblnp problems


Hi all,

I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile. • First,
I tried compiling it on its own - no joy (unresolved symbol _main - it
wanted to be part of an MFC project). So I start an MFC project and • import
the stub.c file and tell the preprocessor where to find the include. • Again,
no joy. I get the error message

CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

TIA

Tim


    
          
     
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Sat, 7 Sep 2002 13:28:31 GMT
Viewed: 
2060 times
  

Don't get what u mean!

----- Original Message -----
From: "nanobapt" <nanobapt@nordnet.fr>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 5:49 PM
Subject: Re: Winliblnp problems


a ActiveX is easy to written with an other Comm activeX for Windows no ?

nanobapt
----- Original Message -----
From: Shehryar Shaheen <shehryar.shaheen@ul.ie>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 6:31 PM
Subject: Re: Winliblnp problems


To my knowledge nobody has been succesful with WinLNP!

I gave up after a while and now use LNP under Linux.

There was some work that somboby did which allowed the deamon
to run on Linux but the LNP program could be run under windows.

U could do a search in the mailing list archives.

Hope this helps

PS  If u get WinLNP to work , let every one know how u did it!

----- Original Message -----
From: "Tim Auton" <tim.lugnet@uton.org>
To: <lugnet.robotics.rcx.legos@lugnet.com>
Sent: Friday, September 06, 2002 4:07 PM
Subject: Winliblnp problems


Hi all,

I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile. • First,
I tried compiling it on its own - no joy (unresolved symbol _main - it
wanted to be part of an MFC project). So I start an MFC project and • import
the stub.c file and tell the preprocessor where to find the include. • Again,
no joy. I get the error message

CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

TIA

Tim


   
         
   
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Tue, 10 Sep 2002 00:45:02 GMT
Viewed: 
2008 times
  

From: "Tim Auton" <tim.lugnet@uton.org>
Sent: Friday, September 06, 2002 4:07 PM
I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile • [snip]
I get the error message
CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

I do, it's a namespace problem, down to you working in a C++ project and
winliblnp being in C. I suggest a quick and dirty hack of creating a
duplicate liblnp.h (called, say liblnpcpp.h) with extern "C" in front of all
the function declarations. It's dirty because you'll still need to keep the
existing liblnp.h around as it's referenced in stub.c. It is of course bad
programming practice to have two copies of something more or less identical
around and you really should read a book on C++. That one you bought, for
example. But hey, it's 1.45 am and it finally works :)

Tim

   
         
   
Subject: 
Re: Winliblnp problems
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Tue, 10 Sep 2002 23:40:27 GMT
Viewed: 
2197 times
  

In lugnet.robotics.rcx.legos, Tim Auton writes:
From: "Tim Auton" <tim.lugnet@uton.org>
Sent: Friday, September 06, 2002 4:07 PM
I recently downloaded winliblnp, the port by Michael Bunk of liblnp to
windows. Exactly what I needed, thanks Michael.

Unfortunately, I'm rather new to VC++ and I can't get it to compile • [snip]
I get the error message
CamStandDlg.obj : error LNK2001: unresolved external symbol "enum
lnp_init_result  __cdecl lnp_init(char *,unsigned short,unsigned
char,unsigned char,int)" (?lnp_init@@YA?AW4lnp_init_result@@PADGEEH@Z)

Anybody know what I'm missing?

I do, it's a namespace problem, down to you working in a C++ project and
winliblnp being in C. I suggest a quick and dirty hack of creating a
duplicate liblnp.h (called, say liblnpcpp.h) with extern "C" in front of all
the function declarations

The usual method is to put the following near the top of the .h file:

#ifdef __cplusplus
extern "C" {
#endif

and the following at the bottom:

#ifdef __cplusplus
}
#endif

This eliminates the need for 2 .h files. HTH.

ROSCO

 

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR