Serious developer questions regarding VLC code tree on Win32
Posted: 28 May 2007 17:54
I'm a developer seeking some definitive answers on the VLC code tree + VC compilers...
Before you reply:
1. Yes, I know it's best to compile VLC under Cygwin or MingW (I have done so many times), that isn't my question
2. Yes, I know not all of the libraries can be compiled under MSVC
3. Yes, I know you probably don't like the MS tools, I don't either particularly so you don't need to convince me otherwise
4. Yes, I have searched the forum for this info to no avail
So the context of my question is this:
We *need* to compile a minimal build of VLC with either VC6, 7 or 8 (VS2005). I don't care which.
We need to build it that way so we can use MS debugging tools. The DLL's we have to use are compiled under MSVC and they simply can't be ported to cygwin (they use hardware). Therefore GDB/Insight doesn't cut it, it won't step into our code and hosting a cygwin compiled VLC under MSVC debugger causes all sorts of problems (it bombs out randomly, locks up randomly, and not least the debug symbols from GCC can't be exported to MS debuggers).
We don't need a full build of VLC, we only need whatever it takes to decode an AVI, or MP4 file. We don't need decoder support, we'll be providing that, so lack of the FFMPEG library isn't the end of the world. This is simply to allow a workable development process for the rather cool project our team are working on.
So this leads onto my questions:
1. Which is the best version of the tree to use to try and do this?
2. Which is the easiest compiler to do it with, VC6, VS.Net or VS2005?
3. I've figured out how to build the .dsp's or .vcproj's with toolbox but they don't compile, I get this error plus many more...
..\include\vlc_symbols.h(482) : error C2061: syntax error : identifier 'lldiv_t'
(this was on the 0.8.6b tree with VC6)
Do I need to move files around, set special #defines or pass special options to ./bootstrap to make this work?
4. Any tips on which modules do and don't compile easily.
Before you reply:
1. Yes, I know it's best to compile VLC under Cygwin or MingW (I have done so many times), that isn't my question
2. Yes, I know not all of the libraries can be compiled under MSVC
3. Yes, I know you probably don't like the MS tools, I don't either particularly so you don't need to convince me otherwise
4. Yes, I have searched the forum for this info to no avail
So the context of my question is this:
We *need* to compile a minimal build of VLC with either VC6, 7 or 8 (VS2005). I don't care which.
We need to build it that way so we can use MS debugging tools. The DLL's we have to use are compiled under MSVC and they simply can't be ported to cygwin (they use hardware). Therefore GDB/Insight doesn't cut it, it won't step into our code and hosting a cygwin compiled VLC under MSVC debugger causes all sorts of problems (it bombs out randomly, locks up randomly, and not least the debug symbols from GCC can't be exported to MS debuggers).
We don't need a full build of VLC, we only need whatever it takes to decode an AVI, or MP4 file. We don't need decoder support, we'll be providing that, so lack of the FFMPEG library isn't the end of the world. This is simply to allow a workable development process for the rather cool project our team are working on.
So this leads onto my questions:
1. Which is the best version of the tree to use to try and do this?
2. Which is the easiest compiler to do it with, VC6, VS.Net or VS2005?
3. I've figured out how to build the .dsp's or .vcproj's with toolbox but they don't compile, I get this error plus many more...
..\include\vlc_symbols.h(482) : error C2061: syntax error : identifier 'lldiv_t'
(this was on the 0.8.6b tree with VC6)
Do I need to move files around, set special #defines or pass special options to ./bootstrap to make this work?
4. Any tips on which modules do and don't compile easily.