Bug 49655 - [Qt] using compiler flag /EHsc breaks build webkit 2.0
Summary: [Qt] using compiler flag /EHsc breaks build webkit 2.0
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P5 Minor
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks:
 
Reported: 2010-11-17 04:28 PST by bleukousuke
Modified: 2011-01-20 08:13 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bleukousuke 2010-11-17 04:28:01 PST
I stumbled on this when compiling qt4.7 with msvc9
earlier versions use /GX as standard

How to reproduce:
compiling qtwebkit 2.0 trunk (seperate not qt4.7) without /EHsc 
compiling qtwebkit 2.0 trunk with environment variable CL= /EHsc

/EHsc is standard in msvc9
 and optional in msvc8

the code warning in the end of qtwebkit2.0 claims something in the code isnt usable with /EHsc
and a macro redefinition of _HAS_TR1 is also solved when not using /EHsc

but this is not to be taken literally

because if you use msvc10 it should use /EHsc as standard
I had it also as an environment variable (by mistake)
when this is the case, the build fails
but when I remove the environment variable
it works like a charm

Funny enough
qt4.7 has the same problem as msvc2008
with the environment variable

and msvc2010 without the environment variable

I'll post some logs as a follow-up later
Comment 1 Benjamin Poulain 2011-01-14 11:09:29 PST
Please follow this to report bugs on QtWebKit: http://trac.webkit.org/wiki/QtWebKitBugs

I do not understand any of this, maybe Jocelyn will know :)
Comment 2 bleukousuke 2011-01-20 08:08:22 PST
Hi, i'll make a new bug post then later
I was a bit confused when I was writing this bug
so I said some things wrong :p
Comment 3 Benjamin Poulain 2011-01-20 08:13:20 PST
(In reply to comment #2)
> Hi, i'll make a new bug post then later
> I was a bit confused when I was writing this bug
> so I said some things wrong :p

Ok, closing this one if it is not accurate. Do not forget to use the template when you open the next one: http://webkit.org/new-qtwebkit-bug