Re: Dropping support for Visual Studio 2008 in master branch

Regina Henschel <rb.henschel -AT- t-online.de>
Wed, 29 May 2013 16:28:09 +0200

Hi Tor,

Tor Lillqvist schrieb:

Unless somebody can give a *really* good reason, I plan to explicitly
drop support for building the master branch with MSVS 2008 soon.

It might be that this support was already unintentionally broken earlier
today or yesterday, and it would be easiest to just follow up and do it
completely.

Note that already the TDF 4.0 build has been built with MSVS 2010.

Is a build possible with the Express version, on Windows 7, so that itincludes ATL?


Kind regards
Regina

Context

Dropping support for Visual Studio 2008 in master branch · Tor Lillqvist
- Re: Dropping support for Visual Studio 2008 in master branch · Regina Henschel
  - Re: Dropping support for Visual Studio 2008 in master branch · Thomas Arnhold
    - Re: Dropping support for Visual Studio 2008 in master branch · Mat M
      - Re: Dropping support for Visual Studio 2008 in master branch · Thomas Arnhold
  - Re: Dropping support for Visual Studio 2008 in master branch · Michael Stahl
    - Re: Dropping support for Visual Studio 2008 in master branch · Mat M
      - Re: Dropping support for Visual Studio 2008 in master branch · Andras Timar
        
        Re: Dropping support for Visual Studio 2008 in master branch · Mat M
        
        Re: Dropping support for Visual Studio 2008 in master branch · Tor Lillqvist

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.