1

Topic: Re: MySQL 5.7 and a Visual C ++. A problem with

Hello, Jura, you wrote: > Decided to try to make the project on a Visual C ++ (2017 studio) which would work with MySQL. > Downloaded MySQL 5.7, all delivered. Data Connection in studio sees basis, sees the circuit, sees tables. > Installed a Visual Studio connector, Connector/Net, Connector/C ++. All under the instruction the link. > the Most simple project not . Writes the such: > Jura> LNK4098 defaultlib ' MSVCRT ' conflicts with use of other libs; use/NODEFAULTLIB:library SecondTry D:\dev_projects\VCPP\SecondTry\SecondTry\LINK 1 Most likely, it is necessary to collect anew these libraries for connectivity c MySQL (or to search collected in a network) under MS VC 2017. Probably, those are collected with earlier versions VC which use other version CRT. Also probably you confuse debug and  versions of these libraries.

2

Re: Re: MySQL 5.7 and a Visual C ++. A problem with

Hello, Jura, you wrote: > All under the instruction the link. > Tried that could, different type Runtime Library (MD/MDd etc) - I can not overcome. To dock it is readable and done strictly on it: Choose the a C ++ Runtime Library to link to. In the Property Pages dialog, open a C ++, Code Generation in the tree view, and then select the right option for Runtime Library following these rules: For the Community version of Connector/C ++: For version 1.1.8 and before: Link to the static version of the a C ++ runtime by selecting the/MT compiler option. For version 1.1.9 and later: Link to the dynamic version of the a C ++ runtime by selecting the/MD compiler option. Also, target hosts running the client application need to have the a Visual C ++ Redistributable for a Visual Studio 2013 installed. For the Commercial version of Connector/C ++: Link to the static version of the a C ++ runtime by selecting the/MT compiler option. Do NOT use the/MTd or/MDd option if you are using the Oracle-built Connector/C ++; see the discussion here for an explanation.