|
|
| BitBasher |
| Posted: May 31 2010, 12:33 AM |
 |
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22242
Joined: 12-October 07
|
It's been a while since I've built VD, and this try was better - newer VD version, newer compiler and toolchain, etc helped. I have a few minor suggestions that might help make the Out-of-box experience of compiling/building VD a teeny bit more enjoyable. 
I'm using VS2008 without the WindowsSDK or older PlatformSDK (just the native VS2008 install) and the Feb 2010 DX SDK. My VS2008 has SP1 installed. I've played a bit with VS2010 in a VM, but so far I'm not ready to take the VS2010 plunge yet since it's different in a way-I-can't-quite-pinpoint and some of our larger VS200x projects do NOT port well to VS2010.
1. Have you entertained the idea of adding a "dummy" dxtrans.h file to the src\Riza\h folder?
If a dummy dxtrans.h file containing only:
| CODE | #define __IDxtCompositor_INTERFACE_DEFINED__
#define __IDxtAlphaSetter_INTERFACE_DEFINED__
#define __IDxtJpeg_INTERFACE_DEFINED__
#define __IDxtKey_INTERFACE_DEFINED__
|
is placed in Riza's h folder, then one can build with DX SDKs newer than Aug 2007 (which was the last DX SDK to include dxtrans.h). I can build VD (with the dummy dxtrans.h file) using DX SDK Feb 10 - and it seems to be ok. 
2. Is it possible to produce VD source archives wihout the READONLY flag set?
This one always bits me, sometimes with strange errors in the past. Converting the VS2005 project to VS2008 requires all the .sln and .vcproj files to be read/write.
3. I have one undefined constant, MIIM_FTYPE, in src\system\source\w32assist.cpp
This one might be my fault, for not having the WindowsSDK installed - I only have the built-in SDK that comes stock with VS2008. Or is this a funky WinCE thingy?
Perhaps a:
| CODE | #ifndef MIIM_FTYPE
#define MIIM_FTYPE 0x100
#endif
|
construct might be helpful - unless you hate those.  Where is this sucka defined anyways?
4. If I do a CLEAN build in VS2008, some ?needed? files are deleted.
For some reason, when I do a clean build in the IDE, a bunch of .inl files are nuked, and then they are not regenerated on build resulting in build errors - missing files. Is there a step I need to do before starting a build after a clean to re-gen these files?
5. Is VS2008 evil?
This is just a question really. I seem to be able to build and run VD with VS2008. Any reason you're sticking with VS2005 and/or are there any issues with VS2008 I should know about?
Of course, VD rocks, and these are just teeny-weeny minor suggestions!  Now all I need is a cross-reference cheat-sheet so I can figure out what priss, asuka, riza, and the rest of the gang are really doing (I think riza is something-capture-dx9ish related).
Thanks,
Bit.
|
|
| phaeron |
| Posted: Jun 1 2010, 12:07 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
I decided to skip VS2008 Pro because I didn't feel it was worth the price. Practically the only new feature I would have been interested in is intrinsics support for SSE3/SSSE3. There are unfortunately downsides to VS2008, including:
- Executables cannot run on Windows 98/ME or NT4. VirtualDub still supports these platforms.
- Intrinsics code generation got worse due to some heavy-handed bug fixes. In some cases it is drastically worse (3x over VS2005!).
At this point it doesn't look like I'll be upgrading to VS2010 Pro, for much the same reasons... and because the new IDE and project systems need some bug fixing first. I have VC9 and VC10 Express installed, but those don't cut it for VirtualDub development (biggest problem is no resource editor).
The reason that the files are zipped read-only is because they're packed off my development clientspec. What I should probably do is stage the files in a separate directory and zip that.
|
|
|
