Which compiler for the Win32 port ?
Jon Lech Johansen
jon-vl at nanocrew.net
Tue May 22 12:33:07 CEST 2001
On Mon, May 21, 2001 at 10:00:09PM +0100, Gildas Bazin (gbazin at netcourrier.com) wrote:
> Hello everybody,
>
> More people are now working on the Win32 port and funnily enough everybody
> seems to be working with a different compiler (Mingw32, Bcc, Microsoft
> visual C).
You can add Intel c compiler to that list as well :)
> - We should not use specific Win32 API functions whenever we can do
> otherwise (ie: almost always). That means using the Microsoft Visual C
> Run-Time (MSVCRT) instead. I guess MSVCRT functions introduce some overhead
> compared to the native functions but this shouldn't be a bottleneck and it
> will help to keep the VLC code clean.
Agreed.
> - As I understand it, only Mingw32 has header files which are doing a
> direct mapping between the names of the MSVCRT functions and their ANSI C
> counterparts (eg: _read => read). Thus we'll have to build an header file
> whith such mappings for the ANSI C functions used in the VLC and include it
> when compiling with Bcc or MSVC.
This is not necessary when using the header files included with MSVC.
--
Jon Johansen
nanocrew.net
More information about the vlc-devel
mailing list