MSVC Update

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

MSVC Update

George Karalis
Hello,

This is an update of the current MSVC task. So far I had success in integrating MSVC 2015
to the project but it requires Windows SDK 8.1 or higher in order to work correctly. I ‘ve
found that Microsoft has reworked the folder structure of this SDK so it requires additional
work to be done in the configure.ac, in order to find the correct compilers and tools. Same
thing at the Windows 10 SDK, which has a more different structure.

Another thing that requires additional work is the integration of MSVC 2017. I was able to
find the installation from the registry, using oowintool, copy the required dll etc., but in Visual
Studio 2017 the folder structure is completely different, so changes are also needed at
configure.ac, for —with-cl-home to work correctly.

So that leaves me with the following notes:

(1) Integrate MSVC 2010 with Windows 7.1 SDK, both are available from Microsoft, no
     additional work is needed at the configure level, and update the project to MSBuild
     (Easy)

(2) Integrate MSVC 2017 with Windows 10 SDK, requires more work, but it ’s the main
     goal.

I ‘m thinking of doing an incremental integration. Work on option (1) and after a successful build
continue to option (2). Option (1) also provides support for Windows XP, so we could stick at
that for a while. After (1) is complete I presume that building to a new compiler and SDK, will
be easier, since the project will have already changed to MSBuild.

What are your thoughts and suggestions about this matter?

Kind regards,
George
Reply | Threaded
Open this post in threaded view
|

Re: MSVC Update

Matthias Seidel
Hello George,

Am 10.10.2018 um 13:23 schrieb George Karalis:
> Hello,
>
> This is an update of the current MSVC task. So far I had success in integrating MSVC 2015
> to the project but it requires Windows SDK 8.1 or higher in order to work correctly. I ‘ve
> found that Microsoft has reworked the folder structure of this SDK so it requires additional
> work to be done in the configure.ac, in order to find the correct compilers and tools. Same
> thing at the Windows 10 SDK, which has a more different structure.

Thank you for your work!
Windows is the main platform for our users with about 85% of downloads.
Still is has been a bit neglected...
A newer SDK/compiler will certainly help us on our way to a 64-bit version.

>
> Another thing that requires additional work is the integration of MSVC 2017. I was able to
> find the installation from the registry, using oowintool, copy the required dll etc., but in Visual
> Studio 2017 the folder structure is completely different, so changes are also needed at
> configure.ac, for —with-cl-home to work correctly.
>
> So that leaves me with the following notes:
>
> (1) Integrate MSVC 2010 with Windows 7.1 SDK, both are available from Microsoft, no
>      additional work is needed at the configure level, and update the project to MSBuild
>      (Easy)
This is the SDK we are talking about?
https://www.microsoft.com/en-us/download/details.aspx?id=8279

As a non developer I would say this should be our first step.

>
> (2) Integrate MSVC 2017 with Windows 10 SDK, requires more work, but it ’s the main
>      goal.
>
> I ‘m thinking of doing an incremental integration. Work on option (1) and after a successful build
> continue to option (2). Option (1) also provides support for Windows XP, so we could stick at
> that for a while. After (1) is complete I presume that building to a new compiler and SDK, will
> be easier, since the project will have already changed to MSBuild.

Sounds like a plan to me.
And I also think it would be good if we can support XP for some
additional time.

Regards,
   Matthias

>
> What are your thoughts and suggestions about this matter?
>
> Kind regards,
> George



smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: MSVC Update

Gavin McDonald-3
Please consider filing an INFRA ticket with any new software versions that
might be needed on the Buildbots.
Also eqnuire about an extra 16.04 buildbot if needed.

Gav...


On Sat, Oct 13, 2018 at 9:31 PM Matthias Seidel <[hidden email]>
wrote:

> Hello George,
>
> Am 10.10.2018 um 13:23 schrieb George Karalis:
> > Hello,
> >
> > This is an update of the current MSVC task. So far I had success in
> integrating MSVC 2015
> > to the project but it requires Windows SDK 8.1 or higher in order to
> work correctly. I ‘ve
> > found that Microsoft has reworked the folder structure of this SDK so it
> requires additional
> > work to be done in the configure.ac, in order to find the correct
> compilers and tools. Same
> > thing at the Windows 10 SDK, which has a more different structure.
>
> Thank you for your work!
> Windows is the main platform for our users with about 85% of downloads.
> Still is has been a bit neglected...
> A newer SDK/compiler will certainly help us on our way to a 64-bit version.
>
> >
> > Another thing that requires additional work is the integration of MSVC
> 2017. I was able to
> > find the installation from the registry, using oowintool, copy the
> required dll etc., but in Visual
> > Studio 2017 the folder structure is completely different, so changes are
> also needed at
> > configure.ac, for —with-cl-home to work correctly.
> >
> > So that leaves me with the following notes:
> >
> > (1) Integrate MSVC 2010 with Windows 7.1 SDK, both are available from
> Microsoft, no
> >      additional work is needed at the configure level, and update the
> project to MSBuild
> >      (Easy)
>
> This is the SDK we are talking about?
> https://www.microsoft.com/en-us/download/details.aspx?id=8279
>
> As a non developer I would say this should be our first step.
>
> >
> > (2) Integrate MSVC 2017 with Windows 10 SDK, requires more work, but it
> ’s the main
> >      goal.
> >
> > I ‘m thinking of doing an incremental integration. Work on option (1)
> and after a successful build
> > continue to option (2). Option (1) also provides support for Windows XP,
> so we could stick at
> > that for a while. After (1) is complete I presume that building to a new
> compiler and SDK, will
> > be easier, since the project will have already changed to MSBuild.
>
> Sounds like a plan to me.
> And I also think it would be good if we can support XP for some
> additional time.
>
> Regards,
>    Matthias
>
> >
> > What are your thoughts and suggestions about this matter?
> >
> > Kind regards,
> > George
>
>
>

--
Gav...
Reply | Threaded
Open this post in threaded view
|

Re: MSVC Update

George Karalis
Hello,

I have been testing for a while now, the MSVC 2010 compiler and the Windows 7.1 SDK, with OpenOffice.
While I configured the project correctly finding the correct compiler and SDK, I build the project and while,
most of the modules build successfully with several warnings on the new compiler, others refuse to build
so I am having trouble continuing to a full correct build. More specific the project’s external gtest library,
produces errors, while building. In a thread in gtest i have found that a certain version of gtest fails with
the MSVC 2010 compiler.

I enclose a config log of the configuration with the MSVC 2010 compiler. All in all, the migration seems 
to work fine except on several modules. I thought that I was fairly close, but it seems that more build 
tests are needed in order to generate a correct build.

Best regards,
George




On 14 Oct 2018, at 13:09, Gavin McDonald <[hidden email]> wrote:


Please consider filing an INFRA ticket with any new software versions that
might be needed on the Buildbots.
Also eqnuire about an extra 16.04 buildbot if needed.

Gav...


On Sat, Oct 13, 2018 at 9:31 PM Matthias Seidel <[hidden email]>
wrote:

Hello George,

Am 10.10.2018 um 13:23 schrieb George Karalis:
Hello,

This is an update of the current MSVC task. So far I had success in
integrating MSVC 2015
to the project but it requires Windows SDK 8.1 or higher in order to
work correctly. I ‘ve
found that Microsoft has reworked the folder structure of this SDK so it
requires additional
work to be done in the configure.ac, in order to find the correct
compilers and tools. Same
thing at the Windows 10 SDK, which has a more different structure.

Thank you for your work!
Windows is the main platform for our users with about 85% of downloads.
Still is has been a bit neglected...
A newer SDK/compiler will certainly help us on our way to a 64-bit version.


Another thing that requires additional work is the integration of MSVC
2017. I was able to
find the installation from the registry, using oowintool, copy the
required dll etc., but in Visual
Studio 2017 the folder structure is completely different, so changes are
also needed at
configure.ac, for —with-cl-home to work correctly.

So that leaves me with the following notes:

(1) Integrate MSVC 2010 with Windows 7.1 SDK, both are available from
Microsoft, no
    additional work is needed at the configure level, and update the
project to MSBuild
    (Easy)

This is the SDK we are talking about?
https://www.microsoft.com/en-us/download/details.aspx?id=8279

As a non developer I would say this should be our first step.


(2) Integrate MSVC 2017 with Windows 10 SDK, requires more work, but it
’s the main
    goal.

I ‘m thinking of doing an incremental integration. Work on option (1)
and after a successful build
continue to option (2). Option (1) also provides support for Windows XP,
so we could stick at
that for a while. After (1) is complete I presume that building to a new
compiler and SDK, will
be easier, since the project will have already changed to MSBuild.

Sounds like a plan to me.
And I also think it would be good if we can support XP for some
additional time.

Regards,
  Matthias


What are your thoughts and suggestions about this matter?

Kind regards,
George




--
Gav...


config_log_msvc_2010_sdk_7.1.txt (38K) Download Attachment
gtest_error_msvc_2010.txt (17K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: MSVC Update

Damjan Jovanovic
Hi George

You can skip the building of gtest by passing --disable-unit-tests to
./configure.

Damjan


On Mon, Dec 17, 2018 at 8:03 PM George Karalis <[hidden email]> wrote:

> Hello,
>
> I have been testing for a while now, the MSVC 2010 compiler and the
> Windows 7.1 SDK, with OpenOffice.
> While I configured the project correctly finding the correct compiler and
> SDK, I build the project and while,
> most of the modules build successfully with several warnings on the new
> compiler, others refuse to build
> so I am having trouble continuing to a full correct build. More specific
> the project’s external gtest library,
> produces errors, while building. In a thread
> <https://github.com/google/googletest/issues/276> in gtest i have found
> that a certain version of gtest fails with
> the MSVC 2010 compiler.
>
> I enclose a config log of the configuration with the MSVC 2010 compiler.
> All in all, the migration seems
> to work fine except on several modules. I thought that I was fairly close,
> but it seems that more build
> tests are needed in order to generate a correct build.
>
> Best regards,
> George
>
>
> On 14 Oct 2018, at 13:09, Gavin McDonald <[hidden email]> wrote:
>
>
> Please consider filing an INFRA ticket with any new software versions that
> might be needed on the Buildbots.
> Also eqnuire about an extra 16.04 buildbot if needed.
>
> Gav...
>
>
> On Sat, Oct 13, 2018 at 9:31 PM Matthias Seidel <
> [hidden email]>
> wrote:
>
> Hello George,
>
> Am 10.10.2018 um 13:23 schrieb George Karalis:
>
> Hello,
>
> This is an update of the current MSVC task. So far I had success in
>
> integrating MSVC 2015
>
> to the project but it requires Windows SDK 8.1 or higher in order to
>
> work correctly. I ‘ve
>
> found that Microsoft has reworked the folder structure of this SDK so it
>
> requires additional
>
> work to be done in the configure.ac, in order to find the correct
>
> compilers and tools. Same
>
> thing at the Windows 10 SDK, which has a more different structure.
>
>
> Thank you for your work!
> Windows is the main platform for our users with about 85% of downloads.
> Still is has been a bit neglected...
> A newer SDK/compiler will certainly help us on our way to a 64-bit version.
>
>
> Another thing that requires additional work is the integration of MSVC
>
> 2017. I was able to
>
> find the installation from the registry, using oowintool, copy the
>
> required dll etc., but in Visual
>
> Studio 2017 the folder structure is completely different, so changes are
>
> also needed at
>
> configure.ac, for —with-cl-home to work correctly.
>
> So that leaves me with the following notes:
>
> (1) Integrate MSVC 2010 with Windows 7.1 SDK, both are available from
>
> Microsoft, no
>
>     additional work is needed at the configure level, and update the
>
> project to MSBuild
>
>     (Easy)
>
>
> This is the SDK we are talking about?
> https://www.microsoft.com/en-us/download/details.aspx?id=8279
>
> As a non developer I would say this should be our first step.
>
>
> (2) Integrate MSVC 2017 with Windows 10 SDK, requires more work, but it
>
> ’s the main
>
>     goal.
>
> I ‘m thinking of doing an incremental integration. Work on option (1)
>
> and after a successful build
>
> continue to option (2). Option (1) also provides support for Windows XP,
>
> so we could stick at
>
> that for a while. After (1) is complete I presume that building to a new
>
> compiler and SDK, will
>
> be easier, since the project will have already changed to MSBuild.
>
>
> Sounds like a plan to me.
> And I also think it would be good if we can support XP for some
> additional time.
>
> Regards,
>   Matthias
>
>
> What are your thoughts and suggestions about this matter?
>
> Kind regards,
> George
>
>
>
>
>
> --
> Gav...
>
>
>