Compiling issue since VS2010 (1 Viewer)

[Jay_UK]

Hi guys,

Since MP1 moved to VS2010 I am having issues compiling the latest SVN.

My PC is Windows7 x64 with MS VS2010.

I am trying to build the filters, but I am getting the following two errors:

Error 1 error MSB3721: The command "yasm -X vc -g cv8 -f Win32 -o "C:\svnroot\mediaportal\trunk\DirectShowFilters\mpc-hc_subs\bin\obj\Release_Win32\system\a_memory.obj" "C:\svnroot\mediaportal\trunk\mediaportal\Core.cpp\mpc-hc_subs\src\thirdparty\VirtualDub\system\source\a_memory.asm"" exited with code 1. C:\svnroot\mediaportal\trunk\mediaportal\Core.cpp\mpc-hc_subs\src\YASM.targets 45 6 system


And...

Error 143 error LNK1181: cannot open input file 'C:\svnroot\mediaportal\trunk\DirectShowFilters\mpc-hc_subs\bin\Release\system.lib' C:\svnroot\mediaportal\trunk\DirectShowFilters\MPAudioswitcher\LINK MPAudioSwitcher


Please help!!!!!

J.

 

[Vasilich]

same for me (well, second error for MPAudioSwitcher project is a consequence of first error happening when trying to compile "system" project).
I am use Win XP SP3 as my dev PC and VS2010 Ultimate. It happens with or without VS2010 SP1 installed.

 

[arion_p]

Do you have YASM installed and configured for VS2010?

 

[Jay_UK]

Hi there,

I did have YASM installed - and it still didnt work.

In the end I think I edited either the props or the target file (can't remember) and specified the full path to the YASM exe file (even though it was in the bin directory)

Everything seems to compile ok (except none of the "internal" plugins are compatible - I was post this issue separately)

Thanks for replying

J.

 

[arion_p]

Yasm has to be placed in the VC\bin folder under the top level Visual Studio folder. Typically this is:

C:\Program Files\Microsoft Visual Studio 9.0\VC\bin

 

[kjarrig]

Hi,
I'm trying to compile the newest version of MePo. Using VS2010, always get the error
Error 5 Could not load file or assembly 'file:///C:/svnroot/mediaportal/MediaPortal.Base/BassRegistration.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format. Line 2293, position 5. C:\svnroot\mediaportal\Configuration\Sections\PluginsNew.resx 2293 5 MediaPortal.Configuration


Any ideas?

Kjartan

 

[edsche]

AW: Re: Compiling issue since VS2010

Hi,
I'm trying to compile the newest version of MePo. Using VS2010, always get the error
Error 5 Could not load file or assembly 'file:///C:/svnroot/mediaportal/MediaPortal.Base/BassRegistration.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format. Line 2293, position 5. C:\svnroot\mediaportal\Configuration\Sections\PluginsNew.resx 2293 5 MediaPortal.Configuration


Any ideas?

Kjartan

ResGen.exe error: An attempt was made to load a program with an incorrect format - The Visual Studio Blog - Site Home - MSDN Blogs

This is a bug in VS2010. It's not fixed in SP1. Looks like they are fixing this not before VS2012...
The bug occurs on 64Bit OS, when developing a project targeting .net framework 3.5 and with reference to a external 32Bit assembly.

I had the same problem with InfoService.

 

[UNOPARATOR]

Hi,
I'm trying to compile the newest version of MePo. Using VS2010, always get the error
Error 5 Could not load file or assembly 'file:///C:/svnroot/mediaportal/MediaPortal.Base/BassRegistration.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format. Line 2293, position 5. C:\svnroot\mediaportal\Configuration\Sections\PluginsNew.resx 2293 5 MediaPortal.Configuration


Any ideas?

Kjartan

I'm having the exact same problem. Also MP-TVSeries' solution is affected by this too (different .resx file giving the same error).
Will try the workarounds when I have some time...

 

[kjarrig]

Would like to know your workaround, I tried these in the link, still no luck. Was trying to update the VS2010 with SP1, but still no luck with that.

 

[UNOPARATOR]

Would like to know your workaround, I tried these in the link, still no luck. Was trying to update the VS2010 with SP1, but still no luck with that.

The workarounds are listed in the link that "edsche" posted.
VS2010 SP1 does NOT resolve this issue.