1

Topic: MS VS2013 for XP

on 2013 studio with 2012. All transited smoothly, behind an exception that the program ceased to be launched on Win XP. What not  with the old project, for sample created new MFC the dialogue project. In  installed V120_xp, Specified in its properties the static assembly. After the assembly the program is not launched on . Produces - is not a valid Win32. On  defined that the program searches in kernel32.dll InitializeCriticalsectionEx () which is not present. Correctly, whence to it to undertake in ! Means  V120_xp in 2013 studios to a bulb? In VS2012 such hogwash was not. At me costs VS2013 Ultimate Update 5. A program collected on 10 Windows. Who, what advises?

2

Re: MS VS2013 for XP

Hello, Vicul, you wrote: V> Proapgredilsja on 2013 studio with 2012. All transited smoothly, behind an exception that the program ceased to be launched on Win XP. V> What not  with the old project, for sample created new MFC the dialogue project. In  installed V120_xp, V> Specified in its properties the static assembly. After the assembly the program is not launched on . V> Produces - is not a valid Win32. V> On  defined that the program searches in kernel32.dll InitializeCriticalsectionEx () which is not present. Correctly, whence to it to undertake in ! Generally all is quite logical: function InitializeCriticalsectionEx () started to be supported from Windows Vista. Remove its call from the code (or replace on InitializeCriticalsection) and all will be OK! Here particulars: https://msdn.microsoft.com/ru-ru/librar … p/ms683477 (v=vs.85).aspx V> Means  V120_xp in 2013 studios to a bulb? No, it not so. In this plan - all is exposed correctly. V> in VS2012 such hogwash was not. In this sense I will not prompt, I used VS2013 and VS2015. Even if call InitializeCriticalsectionEx () "was somehow swallowed" at compilation and  on VS2012, not the fact that it successfully fulfills on Win XP V> At me costs VS2013 Ultimate Update 5. A program collected on 10 Windows. I assume that the assembly on any modern (from Windows-7 and ) OS yields similar result. V> who, what advises? To enter some flag of a preprocessor (for the conditional compilation) which defines - there will be old Windows or not. Approximately so: #ifdef USE_OLD_WIN_XP//If use OLD Windows (Windows XP)://we Do that  is supported on Windows XP... #else//If use contemporary Windows://we Do that is supported on modern Windows... #endif

3

Re: MS VS2013 for XP

Hello, Vicul, you wrote: V> Who, what advises? In VC2015 it is necessary to add a key/D_USING_V110_SDK71_/link/SUBSYSTEM:WINDOWS, 5.01 If quickly  that is archive 72 VC2015 +x64 mfc.src (it will be unpacked in 750). It is installed in flow 1 In a directory usage usage example. It collects for winxp

4

Re: MS VS2013 for XP

AG> Remove its call from the code (or replace on InitializeCriticalsection) and all will be OK! If all so was simple. In the fighting project the solution totals more than 30 projects. And this  got out on dll-kah with opencv which I collected on the same 2013 with v120-xp. And in a solution opencv for one hundred projects. And all 42 dll go with call InitializeCriticalsectionEx. On a test program, there it where that inside. I in a wizard created dialog box  with two buttons - ok and cancel. Well that it only showed this window. Therefore on any it should be launched on .

5

Re: MS VS2013 for XP

Hello, kov_serg, you wrote: _> Hello, Vicul, you wrote: V>> Who, what advises? _> in VC2015 it is necessary to add a key/D_USING_V110_SDK71_/link/SUBSYSTEM:WINDOWS, 5.01 _> If quickly  that is archive 72 VC2015 +x64 mfc.src (it will be unpacked in 750). It is installed in flow 1 _> In a directory usage usage example. It collects for winxp At me 2013. But for  thanks

6

Re: MS VS2013 for XP

Hello, Vicul, you wrote: AG>> Remove its call from the code (or replace on InitializeCriticalsection) and all will be OK! V> if all so was simple. OpenCV you speak...  we very much on OpenCV, truth all did under Win-7. We applied OpenCV v 2.4 (it and is accessible to this day on https://sourceforge.net/projects/opencvlibrary). I will in passing note that no problems in this plan - neither with MFC, nor with Qt5 at us EXISTING (truth, all under Win-7). V> in the fighting project the solution totals more than 30 projects. And this  got out on dll-kah with opencv which I collected You collected OpenCV v 3.3? If to take earlier version OpenCV, compatible with Win-XP (the same OpenCV v 2.4)? This variant is real? At least, for support Win-XP... V> on the same 2013 with v120-xp. That is, the assembly with calls InitializeCriticalsectionEx transited under  v120-xp? Strange. Perhaps, this material appears is actual: https://github.com/opencv/opencv/issues/9817 V> And in a solution opencv for one hundred projects. And all 42 dll go with call InitializeCriticalsectionEx. That is - a variant of passage but older library OpenCV - it is actual. I do not know, truth, whether it is possible on  in your case. V> on a test program, there it where that inside. I in a wizard created dialog box  with two buttons - ok and cancel. V> Well that it only showed this window. Therefore on any it should be launched on . Sorry, not  the last two lines - what for "dialog box  with two buttons - ok and cancel"??? An essence of this action??? Replaced call InitializeCriticalsection with something another? Or I here not so understood something? Having source codes, I would try to cause all InitializeCriticalsection, instead of InitializeCriticalsectionEx. Certainly, some changes in the existing codes for this purpose be required... Or  earlier library OpenCV v 2.4.

7

Re: MS VS2013 for XP

V>> in the fighting project the solution totals more than 30 projects. And this  got out on dll-kah with opencv which I collected AG> You collected OpenCV v 3.3? By the way - the variant is possible, what assembly OpenCV v 3.3, produced through CMake, applies those or other options forbidden for Win-XP?

8

Re: MS VS2013 for XP

Hello, Vicul, you wrote: V> Hello, kov_serg, you wrote: _>> Hello, Vicul, you wrote: V>>> Who, what advises? _>> in VC2015 it is necessary to add a key/D_USING_V110_SDK71_/link/SUBSYSTEM:WINDOWS, 5.01 _>> If quickly  that is archive 72 VC2015 +x64 mfc.src (it will be unpacked in 750). It is installed in flow 1 _>> In a directory usage usage example. It collects for winxp V> At me 2013. But for  thanks of Hz at me  are not present 2013 on one of machines. But I think that approximately as well as in 2015. https://tedwvc.wordpress.com/2014/01/01 … s-8-x-sdk/

9

Re: MS VS2013 for XP

AG> Sorry, not  the last two lines - what for "dialog box  with two buttons - ok and cancel"??? An essence of this action??? Whether what to check up the option  v120-xp on 2013  works. Results showed - does not work. Therefore while sense flattery in opencv I do not see. I answer a question as gathered opencv - the last version 3.3.0,  on CMake, the option v120-x has been installed and appeared on all projects opencv,  on 2013.

10

Re: MS VS2013 for XP

Hello, Vicul, you wrote: Unfortunately near at hand is not present 2013. Checked up in 2017 mode vc141_xp, received  without InitializeCriticalsection. Probably there is a variant to update the compiler?

11

Re: MS VS2013 for XP

Hello, Vicul, you wrote: whether V> V> What to check up the option  v120-xp on 2013  works. Results showed - does not work. Therefore while sense flattery in opencv V> I do not see. 1) the option v120-xp on MSVC-2013 Update 5 works. Simple dialogue application - gathers, launched (tried under Win-7, now there is no near at hand a possibility to launch on Win-XP). Earlier, couple of years back,  on MSVC-2013 (v120-xp) I led for a product developed then by me, on old operation: http://www.ensytech.com/sistemnye_reshe … snabzhenie (MFC, in a solution some tens projects). Then all was successfully checked in operation under XP. 2) For MSVC-2013 if application uses not Unicode, it is necessary to download a special packet of support MFC MBCS: https://www.microsoft.com/en-us/downloa … x?id=40770 it is quite possible that here (in this case) it is actual. 3) what Windows version SDK is installed at you on a computer? It also can be a problem: https://stackoverflow.com/questions/278 … ted-errors 4) at the File targetver.h in the project - look that in it...

12

Re: MS VS2013 for XP

V> Who, what advises? I will answer here to everything, 1. Whether works  v120-xp on 2013? Works, I made the test console application, type Hello World. OS  reacts to switching, all means - apprx. 2. Why  did not fulfill test MFC application. Up to the end did not understand - simply if to create from zero mfc a window, it forms without support . But in all programs which I  with 2012,  worked. There will be time  and before. 3. Why Opencv 3.3.0 does not work on XP. Will not work. https://github.com/opencv/opencv/issues/9817 there in clear they wrote - that this problem is and  it they do not gather. It was necessary  on opencv 2.4.6, I hope  it in upcoming version of my program in which will not be . All thanks for the help

13

Re: MS VS2013 for XP

Hello, Vicul, you wrote: V> It was necessary  on opencv 2.4.6, I hope  it in upcoming version of my program in which will not be . In the code opencv only in cap_msmf.hpp it is used InitializeCriticalSectionEx without #if-#else. If XP it is necessary that it is possible to add by analogy with remaining and to try to collect. Will work, push change in an official repository.