Upgrading release compiler to VS2008

Main development forum.

Upgrading release compiler to VS2008

Postby kimmov » Mon Dec 29, 2008 3:11 pm

This was already discussed in developers-mailing list long ago. I've just not had time (or good spot) to do this conversion. I've bought new laptop and it runs Vista so VS2003 doesn't even work in this machine. So this was the point I want to make the VS2008 the first-class compiler for WinMerge.

As I've understood most developers are already using VS2005 or VS2008. So this should not be a big change for most of the people. Most of the work is for me doing all updates to installer runtimes, etc etc.

VS2003 support won't be dropped or deprecated. I'll will do occasional checks that VS2003 works. But for now on code MUST work in VS2008.

What this means:
  • project files won't be updated to VS2008, they remain in VS2003 format to maintain compatibility
  • trunk releases (2.13.x experimentals) are done with VS2008
  • 2.12 branch releases are done with VS2003
  • Installed runtime files will be updated to VS2008 runtimes
  • VS2005/VS2008 specific code is still strongly discouraged, VS2003 should work equally as compiler

If you don't have VS2008 compiler, please ask somebody to test compiling your patch with it. Compile-breaking patches are likely to be reverted unless quick fix arrives. I'm getting more strict about this.

There is small (?) trick in converting current project files to VS2005/VS2008. Automatic conversion loses the ability to use external manifest files. So the XP/Vista visual styles don't get enabled for compiled executable. To fix this, read manual instructions from /Docs/Developers/Compiling.html or run /Tools/Scripts/fix_manifest.py for the project file.

Another related change is I'll stop packaging runtimes for trunk (2.13 experimental) releases. The installer installs runtimes and most of the users are using installer. Small minority using zip/7z archive files are expected to know what they are doing. They either already have the runtime files or can easily install them separately. There are multiple easy to find download places for those runtime files.
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby kimmov » Mon Jan 19, 2009 6:32 pm

Ok, just found out that VS2008 (runtimes) also drop support for W9X, WME and NT4. :o Didn't expect that but I guess it is in line with MS dropping support for older Windows versions. Dropping support for compiler and libraries makes sure nobody can even compile new software for older Windows versions. :(
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby kimmov » Sat Sep 04, 2010 3:42 pm

I think the day for the update has come. It came because of the bug #3056008. Even though nothing states (yet) that VS2005 runtimes are vulnerable I want to play safe here and use version which is more likely to be updated still.

Luckily this hits mostly the installers. There are no code changes needed.
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby christianlist » Sun Sep 05, 2010 5:24 pm

We certainly don't want anybody to suffer cyberattacks just because we are using an old compiler, so let's play it safe and upgrade to VS2008 as soon as we can.
christianlist
Site Admin
 
Posts: 66
Joined: Thu Sep 11, 2008 5:16 pm
Location: USA

Re: Upgrading release compiler to VS2008

Postby kimmov » Sun Sep 05, 2010 7:36 pm

Yep. I'm going to do this next week and use VS2008 for next experimental release.
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby kimmov » Tue Sep 07, 2010 5:51 pm

Ok, I committed installer changes needed for the update. And build executables from current SVN trunk. Installer sizes unfortunately grew. And I'm wondering if 16 MB size of MSI installer can be right? It practically doubled in size!
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby gerundt » Wed Sep 08, 2010 1:46 pm

How large are the old merge modules? If the merge modules from 2008 are doubled in size too, it can maybe true. :shock:
gerundt
Site Admin
 
Posts: 192
Joined: Wed Sep 24, 2008 8:47 am
Location: Germany

Re: Upgrading release compiler to VS2008

Postby kimmov » Wed Sep 08, 2010 2:04 pm

VS 2008 merge modules are smaller than VS 2005 merge modules. So something weird is going on...
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Re: Upgrading release compiler to VS2008

Postby gerundt » Thu Sep 09, 2010 7:33 am

It seems that the MFC merge module blowing up the setup:

  • Without = 3098 KB
  • With CRT = 4735 KB
  • With MFC = 15204 KB
  • With Both = 16801 KB
gerundt
Site Admin
 
Posts: 192
Joined: Wed Sep 24, 2008 8:47 am
Location: Germany

Re: Upgrading release compiler to VS2008

Postby kimmov » Thu Sep 09, 2010 7:39 am

Then it probably is Wix bug or something. Perhaps we can just zip the MSI file to get it smaller..
kimmov
 
Posts: 562
Joined: Thu Sep 11, 2008 8:51 pm
Location: Finland

Next

Return to Developers

Who is online

Users browsing this forum: No registered users and 1 guest