Ethereal-dev: RE: RE : [Ethereal-dev] Buiding on VC .NET solved yet?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Richard Urwin <RUrwin@xxxxxxxxxxxxxx>
Date: Thu, 15 May 2003 17:10:57 +0100
Thank-you both, I am now compiling and running OK.
I did have a problem with loading capture files (even from a live
capture,) but it turned out to be a bad dll version in the run
directory. Unfortunately, during the process I did build zlib, so I
don't know if that solves anything.

-- 
Richard Urwin, Software Design Engineer
Schenck Test Automation
Braemar Court, 1311b Melton Road, Syston, UK.
rurwin@xxxxxxxxxxxxx




> -----Original Message-----
> From: RABRET Laurent FTRD/DAC/ISS
> [mailto:laurent.rabret@xxxxxxxxxxxxxxxxxxxx]
> Sent: 15 May 2003 15:33
> To: Charlie Duke; Richard Urwin; ethereal-dev@xxxxxxxxxxxx
> Subject: RE : [Ethereal-dev] Buiding on VC .NET solved yet?
> 
> 
> >From my VC++.net release, the /MDd option created dlls and 
> exes but it
> was impossible to use Ethereal correctly: Impossible to open files or
> real-time captures (it was not a ZLIB pb...). Did you encounter such
> problems? If yes, how did you fix them?
> Regards
> Laurent
> 
> 
> -----Original Message-----
> From: Charlie Duke [mailto:cduke@xxxxxxx] 
> Sent: Thursday, May 15, 2003 4:03 PM
> To: 'Richard Urwin'; ethereal-dev@xxxxxxxxxxxx
> Subject: RE: [Ethereal-dev] Buiding on VC .NET solved yet?
> 
> Hi Richard,
> 
> 
> I have successfully built ethereal 0.9.11 with VC++.net (7.0).  If I
> remember correctly, I had to add /MD or /MDd flag to LOCAL_CFLAGS
> variable
> in config.nmake.  In my case it looked like one of the component was
> using a
> different C-runtimes which resulted in link error.  Adding 
> the mentioned
> flag overide the settings for those components.
> 
> 
> --
> Charlie
> 
> 
> -----Original Message-----
> From: Richard Urwin [mailto:RUrwin@xxxxxxxxxxxxxx]
> Sent: Thursday, May 15, 2003 4:07 AM
> To: ethereal-dev@xxxxxxxxxxxx
> Subject: [Ethereal-dev] Buiding on VC .NET solved yet?
> 
> 
> Has anyone managed to build ethereal on Visual C .NET? I get lots of
> unresolved symbols which are libc functions with a __imp__ prefix.
> Someone mentioned this back in September, but I can not now 
> see a reply.
> ISTR it was said at the time that building Ethereal on .NET 
> hadn't been
> checked-out yet and to use VC6.
> 
> There is a thread in the curl archives saying that winmm.lib 
> is required
> to solve this problem. Unfortunately it doesn't seem to solve it for
> Ethereal.
> 
> So before I load up VC6, does anyone know how to get it to work with
> .NET?
> 
> -- 
> Richard Urwin, Software Design Engineer
> Schenck Test Automation
> Braemar Court, 1311b Melton Road, Syston, UK.
> rurwin@xxxxxxxxxxxxx
> 
> 
> 
> 
> ______________________________________________________________
> __________
> This email has been scanned for all viruses by the MessageLabs Email
> Security System. For more information on a proactive email security
> service working around the clock, around the globe, visit
> http://www.messagelabs.com
> ______________________________________________________________
> __________
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
> 
> ______________________________________________________________
> __________
> This email has been scanned for all viruses by the MessageLabs Email
> Security System. For more information on a proactive email security
> service working around the clock, around the globe, visit
> http://www.messagelabs.com
> ______________________________________________________________
> __________
> 

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________