[XviD-devel] Did OutputDebugStringf(const char*, ...) get lost in the Forbidden Forest?

[Kerewin]

Hi,

Yeah, I have latest SDKs MSV v6 + .NET2002/3/5. I have built with VC v6 and
I still had 2 little naughty errors and complete failure of DirectShow
build. Once I put together StrmBase stuff properly and tweaked a little the
VC I gave up and moved onto .Net2k5. Fun and games ensued as Assembly is
required in .Net2K5 to RegSvr32 xvid.ax. Hopeless hours spent with the all
meaningful error R6034... I rebuilt the DLL from scratch which ended up
giving it the correct (embedded) assembly. This is still Unmanaged code!

My version of xvid has zero warnings and zero deprecation...

There were so many typing violations some of which can be removed without
typecasting.

Yeah, latest Nasm is important and it should be stresses "s ain't allowed in
parameter list so knocking out spaces in file path is important too!

Maybe I wasn't the crunchiest cookie in the biscuit tin at the time.

One of the things that occurs to me is that there is not a clear
differentiation on builds between Debug and Release...

I am orf to roll an OutputDebugStringf(lpcstr c,...) coz release 1.1.0 lacks
debug.c. The I am going to have -0.0 cups of coffee.
 
Kerewin.

-----Original Message-----
From: xvid-devel-bounces at xvid.org [mailto:xvid-devel-bounces at xvid.org] On
Behalf Of Michael Militzer
Sent: 14 February 2006 22:24
To: xvid-devel at xvid.org
Subject: Re: [XviD-devel] I would be interested in contributing to XviD...

Hi,

welcome to the list! There's no admission required to contribute to XviD.
So you're very welcome to post your patches and improvements here.

Regarding the MSVC support: actually, I don't find it so bad. Iirc, the 
1.1.0 code compiles out of the box using the MSVC projects (if your setup
is ok: nasm, dshow SDK etc.). I have to admit that I never tried with
.NET 2005 so far. Can you describe what is the problem?

Regards,
Michael


Quoting Kerewin <pyromedia at tiscali.co.uk>:

> Dear xvid-devel,
> 
>  
> 
> I have spent the last 6 weeks with the Koepi 30th Dec release 1.1.0 build.
I
> was surprised to find that the MSVC projects were so awkward, for me
anyway,
> to build.
> 
>  
> 
> I have only just got DirectShow, DSH COM up and running, xvid.ax,
compiling
> up properly for Visual Studio .NET 2005 although the rest of the code has
> been pretty straightforward.
> 
>  
> 
> I guess what I would like to see is greater .NET support and regression
> testing so that intensive automated tests can help validate XviD builds.
> There is a seeming lack of documentation too.
> 
>  
> 
> It is still a little amusing to see -0.0 spilling out of the benchmark
> utility. I have not investigated why as yet. There is also the issue of
the
> missing debug.c file in VFW and the fact that the InstallShield project
has
> not been included in the Koepi 1.1.0 build.
> 
>  
> 
> I have:
> 
>  
> 
> *	25 years programming experience
> *	A Computer Science Hons degree from the University of Edinburgh
> *	A background in JPEG codecs, as well as a variety of video and audio
> applications.
> 
>  
> 
> Can I join the team?
> 
>  
> 
> Kerewin.
> 
>  
> 
>  
> 
> _______________________________________________
> XviD-devel mailing list
> XviD-devel at xvid.org
> http://list.xvid.org/mailman/listinfo/xvid-devel
> 




_______________________________________________
XviD-devel mailing list
XviD-devel at xvid.org
http://list.xvid.org/mailman/listinfo/xvid-devel