Using DLL on WINccOA project

[laurent.brugeaud]

A copy of my dos windows VC12 request

[fmulder]

When you look in your Windows Start menu then you'll see something called 'Developer command prompt for VSxxxx'. When you open this command prompt then the path to cl will be ok.

* Choose 'Developer command prompt for VSxxxx'
* Now type 'cl' and press enter
* it should not display the version number for cl
* Stay in this command prompt
* navigate to c:\\siemens\\....\\API
* start checkapienv
* It should now say that the API_ROOT is ok and that the cl version could be read
* Stay in this command prompt
* Now use the batchfiles to make DLL
* Go to the folder where the solution file is *.sln
* Type the name of the solution. Example. type 'mysolution.sln' and press
* (Always stay inside the command prompt)

Share the fun
Frenk Mulder

[laurent.brugeaud]

First many thanks Frenk to take time to help me.

I started the command prompt. the "cl" command is not valid. and the checkapienv return "cannot determine cl compiler version" again

[fmulder]

Please look in attachment.
You must use the pompt that comes with Visual Studio and not just any prompt !!!!
The prompt that comes with Studio will set the proper 'path' in your command prompt

https://www.winccoa.com/fileadmin/image ... prompt.zip

[Gertjan van Schijndel]

Instead of create a new control extension for each library, you could also try CtrlFFI as mentioned in another topic.

https://www.winccoa.com/fileadmin/image ... lFFI_3.zip

[laurent.brugeaud]

I did it. Sorry my prompt is in french but similar to your's

[laurent.brugeaud]

Frenk Mulder wrote:

Please look in attachment.
You must use the pompt that comes with Visual Studio and not just any prompt !!!!
The prompt that comes with Studio will set the proper 'path' in your command prompt

https://www.winccoa.com/fileadmin/image ... prompt.zip

cl.exe is missing due to an uncomplete installation of C++. I must reinstall it with custom option on VS2015.

[laurent.brugeaud]

I'm not sure about the compatibility with vs2015. I still have error messages when i want to use wincc_OA scripts. I'll try tomorrow with a VS2013 installation. Thanks Frenck or your help

[RonFre]

Hi,
Just woundering if VS2013 did the trick or if you had the same problem with VS2013?

[laurent.brugeaud]

VS2013 instead off 2015 solved the problem with wincc_OA scripts. But problem with the dll came again with the new VS project. I translated my functions directly in winncc_Oa scripts to solve issue.