|
|
| dloneranger |
| Posted: May 24 2012, 11:32 PM |
 |
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Checking the source of Asuka, it does return 0 unless there's an error, but none of it's error values =1
Otoh, (here) there are some doubled up slashes being passed in the filenames
Are the 2010 runtime libraries more sensitive about them?
In the rules, OutputPath was
$(ProjectDir)\autogen\
and to get rid of the doubled slashes it could be changed to
$(ProjectDir)autogen
The good thing is that you can modify psa.cpp for debugging the compile
eg adding a messagebox in the function tool_psa to show the passed file names
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| levicki |
| Posted: May 25 2012, 09:46 AM |
|
|
Advanced Member
Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07
|
This is important news and it is related to this topic so I put it here:
http://arstechnica.com/information-technol...d-on-windows-8/
It won't be possible to use Visual Studio 11 Express to create and compile desktop applications.
Regarding the slashes I have seen only one situation where VS2010 insists on having trailing slashes (for OutDir and IntDir if I remember correctly). |
|
| phaeron |
| Posted: May 27 2012, 08:50 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
| QUOTE | | Anyway, thanks phaeron - that cast did the trick. Well, for that bit anyway - VC++ 10 makes compiling VDub a lot more complicated. I had to put src/ in the root of C:\ to get anywhere - some kind of path macro problem? I also had to run all of the "asuka.exe psa" commands myself on the command line, because they all "exited with code 1". |
The VS2010 project converter is pretty broken and you have to fix up the projects afterward. The problem with files getting dumped in or referenced from the root is caused by property sheet ordering issues -- VS2005/2008 is order independent, MSBuild is not. Reorder the project property sheets in the Property View to fix the problem. I already did this in the 1.10.x sources, but you need to fix this up for 1.9.x.
Backslash issues are due to another ill-advised change, which is that MS decided that the $(IntDir) and $(OutDir) path macros should end in a backslash. I don't know why, because the OS path variables don't have this and it breaks command lines that use quotes around the paths, i.e. "$(IntDir)" and "$(OutDir)". Remove the backslash from the intermediate and output directory settings in the project to fix.
| QUOTE | | command line -> "..\..\out\Debug\asuka.exe" psa "f:\VSProjects\VirtualDubProjects\Virtualdub\src\VirtualDub\VirtualDub.vcproj" "f:\VSProjects\VirtualDubProjects\Virtualdub\src\VirtualDub\\autogen\\VirtualDub.inl" |
Err, this is totally wrong -- it is trying to compile the project file itself. I'm trying to remember what needed to be changed in the PSA rules file... the VS2010 custom build rule converter has tons of bugs.
|
|
| Altaf |
| Posted: Feb 26 2014, 08:26 AM |
|
|
Advanced Member
Group: Members
Posts: 75
Member No.: 36396
Joined: 9-April 13
|
Первый вариант VD я собираю. Как собрать вариант VD - AMD64?
--------------------------------------
I collect the first VD option.
How to compile VD option - AMD64? |
|
