Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#856 closed defect (fixed)

Fix Windows project settings not correctly using /O2 optimization for Release configurations

Reported by: brucedechant Owned by: brucedechant
Priority: low Milestone: 2.1
Component: General Version: 2.0.2
Severity: minor Keywords:
Cc: External ID:

Description

When the Windows projects were migrated from Visual Studio 2005 to Visual Studio 2008 all of the projects that used the /O2 optimization setting for Release configurations were lost. The Visual Studio 2008 UI will even show that /O2 is set, but if you look at the actual command line options it is not being set. This is a known issue with Visual Studio 2008.

Change History (8)

comment:1 by brucedechant, 16 years ago

Owner: set to brucedechant
Status: new → assigned

comment:2 by brucedechant, 16 years ago

Summary: Fix Windows project settings not correctly using /02 optimization for Release configurations → Fix Windows project settings not correctly using /O2 optimization for Release configurations

comment:3 by brucedechant, 16 years ago

r3626 - Oem projects

comment:4 by brucedechant, 16 years ago

r3628 Common projects

comment:5 by brucedechant, 16 years ago

r3629 Server projects

comment:6 by brucedechant, 16 years ago

r3631 Web tier projects

comment:7 by brucedechant, 16 years ago

Resolution: → fixed
Status: assigned → closed

comment:8 by brucedechant, 16 years ago

The following submissions cover the changes to the sandbox/adsk/2.1 branch:

r3645 Oem projects r3646 Common projects r3647 Server projects r3648 Web tier projects

Note: See TracTickets for help on using tickets.