MantisBT - CMake
View Issue Details
0014399CMakeCMakepublic2013-09-11 04:452016-06-10 14:31
Xuefer 
Patrick R. Gansterer 
normalblockalways
closedmoved 
Win32Windows7
 
 
0014399: Can't use assembler files with Visual Studio 11 generator
using nightly 2.8.11.20130910-g7124b
bug 0011536 is really fixed, but with exactly same code using Visual Studio 11 generator, the asm is not compiled
No tags attached.
related to 0011536closed Patrick R. Gansterer Can't use assembler files with Visual Studio 10 generator 
Issue History
2013-09-11 04:45XueferNew Issue
2013-09-11 08:31Brad KingAssigned To => Patrick R. Gansterer
2013-09-11 08:31Brad KingStatusnew => assigned
2013-09-11 08:31Brad KingRelationship addedrelated to 0011536
2013-09-11 18:14Patrick R. GanstererNote Added: 0033804
2013-09-12 00:32XueferNote Added: 0033806
2016-06-10 14:29Kitware RobotNote Added: 0042362
2016-06-10 14:29Kitware RobotStatusassigned => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0033804)
Patrick R. Gansterer   
2013-09-11 18:14   
The simple example from the other bug works for me.
What VS version (express, professional, ...) do you have? Does it support ASM files?
Can you attach a _full_ example and maybe also the generated files?
(0033806)
Xuefer   
2013-09-12 00:32   
sorry to waste your time, i should have remove all generated files before re-run cmake and read the error output twice

the assembler is compiles fine in Visual Studio 11 generator (while it was not in 2.8.11)

9>EasyHookS_asm.lib(HookSpecific_x86.obj) : error LNK2026: module unsafe for SAFESEH image.
9>EasyHookS_asm.lib(ILD_x86.obj) : error LNK2026: module unsafe for SAFESEH image.
test.dll : fatal error LNK1281: Unable to generate SAFESEH image.

I'm now facing a new problem: /SAFESEH seems to be default to on in 2012, while it was off in 2010. not a cmake bug i guess
(0042362)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.