New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 8 link

Starred by 4 users

Issue metadata

Status: Done
Owner:
Last visit > 30 days ago
Closed: Sep 2010



Sign in to add a comment

YASM assembly issues

Project Member Reported by jkoleszar@google.com, May 19 2010

Issue description

Assembly code can not be linked in SAFESEH mode on win32 due to lack of
support in yasm. Also, configuring libvpx with --enable-pic causes bugs
with yasm-1.0.0 that aren't present in yasm-0.8.0
 
Project Member

Comment 1 by jz...@google.com, Jun 3 2010

Saw this [1] referenced in the 1.0.1 changelog, any chance it's related?

[1]: http://www.tortall.net/projects/yasm/ticket/202
Working now on porting the x86/x86_64 .asm part to gas, I should submit it in a day as a GIT Change, I hope it is the approved way to go. GAS is available on all the platforms.

Project Member

Comment 3 by jkoleszar@google.com, Jun 21 2010

Lace,

Suggest mentioning a gas port on the codec-devel list. GAS would remove support for visual studio. What's the issue you're trying to address with a port?

Comment 4 by xudan...@gmail.com, Jul 14 2010

     HI,when i compile the file :vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0,it can not load vpx.vcproj in visual studio 2010.
     the Conversion Report - vpx.vcproj is: 
 Converting project file 'D:\vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0\build\vpx.vcproj'. 
This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project. 
VCConvertEngine.dll encountered an error. 
VCConvertEngine.dll encountered an error. 
VCConvertEngine could not convert attribute ConfigurationType = 4 under Configuration Debug|Win32. 
VCConvertEngine could not convert attribute CharacterSet = 1 under Configuration Debug|Win32. 
The imported project "C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\yasm.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. D:\vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0\build\vpx.vcxproj 
Project upgrade failed. 


 I can not find yasm.targets. When I use vsyasm.targets in stead of yasm.targets,it is wrong ,too.I want to know where is yasm.targets.I should use which version of yasm.targets. Please help me.thank you!


Comment 5 by xudan...@gmail.com, Jul 14 2010

     HI,when i compile the file :vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0,it can not load vpx.vcproj in visual studio 2010.
     the Conversion Report - vpx.vcproj is: 
 Converting project file 'D:\vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0\build\vpx.vcproj'. 
This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project. 
VCConvertEngine.dll encountered an error. 
VCConvertEngine.dll encountered an error. 
VCConvertEngine could not convert attribute ConfigurationType = 4 under Configuration Debug|Win32. 
VCConvertEngine could not convert attribute CharacterSet = 1 under Configuration Debug|Win32. 
The imported project "C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\yasm.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. D:\vpx-vp8-debug-src-x86-win32mt-vs8-v0.9.0\build\vpx.vcxproj 
Project upgrade failed. 


 I can not find yasm.targets. When I use vsyasm.targets in stead of yasm.targets,it is wrong ,too.I want to know where is yasm.targets.I should use which version of yasm.targets. Please help me.thank you!


Project Member

Comment 6 by fgalligan@google.com, Aug 5 2010

Yasm fixed their support for SAFESEH on 2010/8/1

http://www.tortall.net/projects/yasm/ticket/139

It sounds like no change is necessary... just upgrade to yasm 1.1, and code will be safeseh friendly?
We're now using YASM 1.1 to build libvpx on Windows for Firefox with safeseh, so it should work for you guys too.
Project Member

Comment 9 by jkoleszar@google.com, Sep 23 2010

Status: Done
Ok, I think we can close this issue then.
Project Member

Comment 10 by alberto@google.com, Mar 8 2012

Labels: -Type-Defect Type-Bug

Sign in to add a comment