Following Ingo and looking into his install2.sh, I installed Codesys 3.5.17.20 at 64bits on Ubuntu / Linux 20.04 with wine-staging 7.0.
Unlike the version suggested by Ingo, it requires .NET 4.6.2.
Once installed and launched it is very fluid and fast, much more responsive than on any Windows 10 Virtual machine.
However some native library is required, otherwise some things don't work.
For example crypt32, msacm32, crypt32, msasn and the various msxlm, due is not able to recognize the digital signatures with emulated versions, and it's not possible install packges or read correctly the XML ethercat descriptors.
Now il looking in package manager when i installa Linux Runtime Package.
I'ts a problem in thread management! I'm searching if it can solved with some other native dll.
π
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well small snags are expected when you open such a tricky drawer. Nevertheless I personally think this is very π nice.
@ingo please let @mondinmr be able to post these scripting steps in the CODESYS4Linux project. I hope you can add him as an author? Hopefully you'll consider it π
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok! I made many tests! I can also install launching .msi file.
Tests in 32bit gone all in a wrong way. Codesys installs, but not start.
Tests in 64bit are working. Codesys is working, linux gateway is viewed, but remains big problems in cryptographic system.
I see a massive usage of ncrypt.dll, and bcrypt.dll.
Some function in wine ncrypt.dll is missing so XML, packages and libraries signature validation not working at all!
I also try to copy ncrypt.dll from a native Windows10, but after that a new message came up:
api-ms-win-eventing-obsolete-l1-1-0.dll needed by ncrypt.dll was not found.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Following Ingo and looking into his install2.sh, I installed Codesys 3.5.17.20 at 64bits on Ubuntu / Linux 20.04 with wine-staging 7.0.
Unlike the version suggested by Ingo, it requires .NET 4.6.2.
Once installed and launched it is very fluid and fast, much more responsive than on any Windows 10 Virtual machine.
However some native library is required, otherwise some things don't work.
For example crypt32, msacm32, crypt32, msasn and the various msxlm, due is not able to recognize the digital signatures with emulated versions, and it's not possible install packges or read correctly the XML ethercat descriptors.
Now il looking in package manager when i installa Linux Runtime Package.
I'ts a problem in thread management! I'm searching if it can solved with some other native dll.
more posts ...
Hi,
that is wonderful news, can you share a how-to at Tools/Codesys4Linux?
I think many people are interested in running that setup, including me.
There are followed steps:
I downloaded Codesys 3.5.17.20 in zip format "NOT EXE!!!"
Codesys is starting, but I need some other tuning to make package manager working.
I also installed Edge gateway for linux.
In attachment the result!
Last edit: mondinmr 2022-01-18
In following attachment you can see residual problems.
Signatures validation, not working and XML Ethercat are opened in wrong mode!
One of problems is around crypt32 and msasn1! I'm searching to solve deps.
Last edit: mondinmr 2022-01-18
Well small snags are expected when you open such a tricky drawer. Nevertheless I personally think this is very π nice.
@ingo please let @mondinmr be able to post these scripting steps in the CODESYS4Linux project. I hope you can add him as an author? Hopefully you'll consider it π
I installed 2 packages with PackageManagerCLI.exe, but without encryption working I cannot download missing libraries.
Ok! I made many tests! I can also install launching .msi file.
Tests in 32bit gone all in a wrong way. Codesys installs, but not start.
Tests in 64bit are working. Codesys is working, linux gateway is viewed, but remains big problems in cryptographic system.
I see a massive usage of ncrypt.dll, and bcrypt.dll.
Some function in wine ncrypt.dll is missing so XML, packages and libraries signature validation not working at all!
I also try to copy ncrypt.dll from a native Windows10, but after that a new message came up:
api-ms-win-eventing-obsolete-l1-1-0.dll needed by ncrypt.dll was not found.