Hi,
I came across the document saying
An EWO is dynamically loaded into the WinCC OA user Interface(it is compiled as a plugin into shared library dll)
I didnt get this statement, do the user need the lib or plugin for renaming as .ewo?.
Thanks,
Regarding the EWO as a plugin or lib for WinCC OA
- Pradeep Kumar
- Posts:39
- Joined: Fri Dec 09, 2016 2:54 pm
Regarding the EWO as a plugin or lib for WinCC OA
- mkoller
- Posts:741
- Joined: Fri Sep 17, 2010 9:03 am
Re: Regarding the EWO as a plugin or lib for WinCC OA
On Windows, for whatever dubious reason, you get two files: .lib and .dll
What we load is the .dll, but you need to rename it to .ewo
On Linux, there is just one file: .so, so you need to rename this one.
What we load is the .dll, but you need to rename it to .ewo
On Linux, there is just one file: .so, so you need to rename this one.
- Pradeep Kumar
- Posts:39
- Joined: Fri Dec 09, 2016 2:54 pm
Re: Regarding the EWO as a plugin or lib for WinCC OA
@Martin thanks ,
So i will need to create the Qt App as a .dll shared library so that we compile, we get .dll and then we can rename as For Ex : MyApp.ewo. Out the .dll created
Is my understanding clear.
Thanks,
So i will need to create the Qt App as a .dll shared library so that we compile, we get .dll and then we can rename as For Ex : MyApp.ewo. Out the .dll created
Is my understanding clear.
Thanks,
- mkoller
- Posts:741
- Joined: Fri Sep 17, 2010 9:03 am
Re: Regarding the EWO as a plugin or lib for WinCC OA
yes, that's correct.