<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi,<br><br>thanks much for your help<br><br>I used the instructions here <br><br>http://www.cs.tut.fi/~hirvone2/SGN_5106_Exercise4_2009.pdf<br><br>to compile and debug the media server and it run successfully But in the test with any rtsp link it caches !!<br><br>Does anyone know the reason ?<br><br>Thanks.<br><br><div><p class="EC_MsoNormal" style="text-align: left; direction: ltr; unicode-bidi: embed;"><span style="font-size: 8pt; font-family: 'Comic Sans MS'; color: blue;"><a href="http://www.softlock.net/" title="http://www.softlock.net/"><span style="" lang="FR"></span></a></span><span style="color: blue;"></span></p>
<br><br></div><br><br><br><br>> From: patbob@imoveinc.com<br>> To: live-devel@ns.live555.com<br>> Date: Thu, 28 May 2009 09:46:46 -0700<br>> Subject: Re: [Live-devel] Meadia Server on VS 2005 or 2008<br>> <br>> On Wednesday 27 May 2009 11:21 am, Jeremy Noring wrote:<br>> > If I have time, I may try to do this today, since I need this sort of<br>> > functionality for debugging symbols, debug/release builds, x64 support,<br>> > integration into our project, etc. I'll let you know if I have any<br>> > success.<br>> <br>> We needed the same thing, and found a way to generate the PDB files as live555 <br>> builds. Unfortunately, it required mods to the shared build files.<br>> <br>> Basically, the changes were:<br>> <br>> *) add something like "/Fd$(LIBNAME)D.pdb" to the COMPILE_OPTS in the <br>> win32config file. We made two win32config files -- one that's used for <br>> release and doesn't have the option (because we don't want/need PDB files for <br>> release builds) and one for debug that does include it.<br>> <br>> *) Modify Makefile.head in each project to set a LIBNAME variable to the name <br>> of the library being generated. Here's an example from the groupsock <br>> project:<br>> LIBNAME=libgroupsock<br>> <br>> Recompile and you'll get PDB files generated next to the libraries. We move <br>> them all into a libs directory for convenience.<br>> <br>> *) To use them, I ended up copying them into the dir where we have the <br>> compiler put all the generated DLLs, libs and EXEs.<br>> <br>> <br>> What I found was that the PDB files could not be renamed. They could be <br>> moved, but must remain by their original name in oprder for Visual Studio to <br>> be able to use them. That's why I had to modify the Makefile.head files to <br>> have a different LIBNAME in each -- I couldn't generate the PDB files by the <br>> same name for each project and later rename them, and there seemed to be no <br>> other place to quickly and easily get the lib name from. The "D" on the end <br>> of the PDB file name is not really needed, its an artifact of our dev <br>> procedures.<br>> <br>> hope that helps,<br>> patbob<br>> _______________________________________________<br>> live-devel mailing list<br>> live-devel@lists.live555.com<br>> http://lists.live555.com/mailman/listinfo/live-devel<br><br /><hr />check out the rest of the Windows Live™.
More than mail–Windows Live™ goes way beyond your inbox.
<a href='http://www.microsoft.com/windows/windowslive/' target='_new'>More than messages</a></body>
</html>