Changeset 140694 in webkit


Ignore:
Timestamp:
Jan 24, 2013 10:48:35 AM (11 years ago)
Author:
bfulgham@webkit.org
Message:

Get WTF compiling in VS2010 (32bit)
https://bugs.webkit.org/show_bug.cgi?id=106986

Reviewed by Tim Horton.

If you do not have Cygwin in the overall operating system
PATH, the project will not build. In VS2005 we had logic
in the build system to guard against this. We should
retain this in the VS2010 work.

Furthermore, VS2010 has a nasty bug where to Visual Studio
tools path is not defined when performing a 'clean' phase
on an NMAKE-based build. This is corrected here as well.

  • win/tools/vsprops/common.props: Revise environment setup

to ensure proper tools are in path during build.

Location:
trunk/WebKitLibraries
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/WebKitLibraries/ChangeLog

    r140567 r140694  
     12013-01-24  Brent Fulgham  <bfulgham@webkit.org>
     2
     3        Get WTF compiling in VS2010 (32bit)
     4        https://bugs.webkit.org/show_bug.cgi?id=106986
     5
     6        Reviewed by Tim Horton.
     7
     8        If you do not have Cygwin in the overall operating system
     9        PATH, the project will not build.  In VS2005 we had logic
     10        in the build system to guard against this.  We should
     11        retain this in the VS2010 work.
     12
     13        Furthermore, VS2010 has a nasty bug where to Visual Studio
     14        tools path is not defined when performing a 'clean' phase
     15        on an NMAKE-based build.  This is corrected here as well.
     16
     17        * win/tools/vsprops/common.props: Revise environment setup
     18        to ensure proper tools are in path during build.
     19
    1202013-01-19  Roger Fong  <roger_fong@apple.com>
    221
  • trunk/WebKitLibraries/win/tools/vsprops/common.props

    r140567 r140694  
    1010    <IntDir>$(ConfigurationBuildDir)\obj\$(ProjectName)\</IntDir>
    1111    <LinkIncremental>false</LinkIncremental>
    12     <NMakeBuildCommandLine>nmake -f $(ProjectName).make</NMakeBuildCommandLine>
    13     <NMakeReBuildCommandLine>nmake /nologo -f $(ProjectName).make clean
    14 nmake -f $(ProjectName).make</NMakeReBuildCommandLine>
    15     <NMakeCleanCommandLine>REM VS2010 has a known bug where the clean command does not recognize environment variables properly unless explicitly set here
     12    <NMakeBuildCommandLine>%SystemDrive%\cygwin\bin\which.exe bash
     13if errorlevel 1 set PATH=%SystemDrive%\cygwin\bin;%PATH%
     14nmake /nologo -f $(ProjectName).make</NMakeBuildCommandLine>
     15    <NMakeReBuildCommandLine>%SystemDrive%\cygwin\bin\which.exe bash
     16if errorlevel 1 set PATH=%SystemDrive%\cygwin\bin;%PATH%
     17nmake /nologo -f $(ProjectName).make clean
     18nmake /nologo -f $(ProjectName).make</NMakeReBuildCommandLine>
     19    <NMakeCleanCommandLine>%SystemDrive%\cygwin\bin\which.exe bash
     20if errorlevel 1 set PATH=%SystemDrive%\cygwin\bin;%PATH%
     21
     22set PATH=$(VSInstallDir)\VC\bin;%PATH%
     23
     24REM VS2010 has a known bug where the clean command does not recognize environment variables properly unless explicitly set here
    1625set CONFIGURATIONBUILDDIR=$(ConfigurationBuildDir)
    1726nmake /nologo -f $(ProjectName).make clean</NMakeCleanCommandLine>
Note: See TracChangeset for help on using the changeset viewer.