docker info: Client: Version: 25.0.3 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.12.1-desktop.4 Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe compose: Docker Compose (Docker Inc.) Version: v2.24.5-desktop.1 Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe debug: Get a shell into any image or container. (Docker Inc.) Version: 0.0.24 Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe dev: Docker Dev Environments (Docker...
Docker IDE Frozen
Home
codesys ide docker image
Hi Orby, sadly that's not easily possible. You are only allowed to build such an image, when you own a windows license. These are the license terms of DotNet. Cheers, Ingo
codesys ide docker image
The placeholder library 'Standard' could not be resolved.
Cannot find IronPython.Modules.dll
Hi Ingo, I already tried that... Firstly, installation for SP11 does not exist online for download (tried changing URL accordingly). Secondly, I tried installing a locally available .exe of SP11 inside Docker and changing up a few necessary things in install script, but it didn't work. Somewhere here it says that Docker version works only from SP13 onwards for some reason... Like I mentioned, I tried already many many combinations to install this for about a week and couldn't get it to compile the...
Hi Paula! That should be as easy, as changing the URL in install2.sh. The variable is called CDS_LINK, and it contains the SP16 version number. I didn't test it with SP11, but guess it should simply work...
Add prerequisite check wine 6.x
Add prerequisite check for cabextract in install2.sh
Add prerequisite check for jwm in install2.sh
Update download command with -O option
Inquiry to build a CODESYS image for RE
Compiling SP11 Project
Error while building project
Thanks for diving into the rabbit whole. 😉 I now improved the error reporting and stability of build-bootapp. Hint: You can call it like this, from the folder of your *.project file... docker run -v $(pwd):$(pwd) -w $(pwd) codesys-ide codesys build-bootapp
heavily improved error reporting when creating a boot application
Potential issue with codesys using updated vcrun files from MS download
After going down the rabbit hole long enough I have found a temporal solution for my problem. Issue Summary: I want to compile CODESYS projects for "CODESYS Control Win V3" devices through CI/CD with a docker container from this repo. The problem is that the docker container does not find the references to some libraries even though they are installed. How to reproduce the issue: 1) Create a new CODESYS project (3.5.16.0 x86) in a Windows machine through the project wizard. It is worth mentioning...
Just an update. I have looked in more detail the output of the CODESYS cli and when I open a .project file (Without archiving) I get also an error.The eror occurs when with the python Script engine API I trying to generate the project (i.e., open(),generate_code()) Build: Error: C188: Device not installed to the system. No code generation possible. Build: Text: C0: Typify code... Build: Warning: C100: Library IoStandard has not been added to the Library Manager, or no valid license could be found...
Error while building project
Home
fixed installation in bullseye, where we don't need wine-development anymore, and codemeter-lite is not supported anymore.
updated to bullseye, but went back to SP16 for the IDE, as SP17 is not usable atm.
switch to SP17
updated install2.sh to use new wine version (>5.x), which is included in the current stable debian
fixed handling of codesyscontrol script of subdirectories
fixed filename, when using subfolders
corrected build script name in test
improved error reporting of buildtest
package install still doesn't work on server, so I felt back to define the required libs only
fixed issue in dependency resolver
corrected entry of unit tests
added drone yaml file to execute unit tests for the CODESYS IDE image
Implemented unit testing against CODESYS Linux SL runtime.
Merge branch 'master' of https://forge.codesys.com/git/tol,codesys-4-linux,docker
- support for CODESYS Linux SL inside of this container
Ticket moved from /forge/support/64/
reverted change, that no XVFB was started anymore for noUi builds (didn't work on headless server)
corrected but in "build package". The package was recursivly added to itself under some circumstances.
- implemented update device
- added unit test draft
Home
A good solution! Well done also on getting SP16 working.
CODESYS V3.5.16.0 not working
Works again! Was just a DotNet issue. winetricks was not able to install DotNet completely headless anymore. So we now have the workaround with xvfb in install2.sh, like we had for install.sh.
Windows license required
While I was updating the installer for SP16 w/ new DotNet, I also added a --silent flag to it. Without that, the installer will show the usual prompt of the DotNet runtime. Futhermore we don't have a need for the Visual C++ Redistributable binaries anymore. The reason is: We just needed them to satisfy our Setup tool. But as install2.sh doesn't use the setup anymore, we don't need the Redistributable packages.
Home
- cleaned docker file and upgraded it to buster
turned dockerfile into a single stage build
Merge branch 'master' of https://forge.codesys.com/git/tol,codesys-4-linux,docker
- kill xvfb instead of terminating. Otherwhise docker hangs for some reasons (The xvfb handling is not that clean, yet ;) )
Another test showed that the IDE worked natively on buster. Seems that we only have problems with the docker images.
CODESYS V3.5.16.0 not working
- prepared CODESYS start script for new profile names (*.profile.xml)
added error messages in case a compile error occured
implemented handling of library dependencies for the "runtest" action
Thanks Ian! First I added a note to the Wiki. Second I plan to show the license by default on install.
Home
Windows license required
added action to save a project archive
Added action to install CODESYS packages.
disabled prompts for "runtest" action, which is running in UI mode
implemented "runtest" action
Installer doesn't work on current debian
I found a much easier way to install CODESYS in wine. I don't run the installer, but extract the files. This method avoids all the endless installer issues and workarounds. It is implemented atm. in codesys-ide/install2.sh. @i-campbell might be of interest for your mac project.
I found a much easier way to install CODESYS in wine. I don't run the installer, but extract the files. This method avoids all the endless installer issues and workarounds. It is implemented atm. in codesys-ide/install2.sh. @i-cambell might be of interest for your mac project.
- added new (much, much, much simplified) install routine
Home
Installer doesn't work on current debian
Docker Image still works. This has only the current issue, that libdoc is missing somehow.
zip html docu correctly (it wasn't zipped, as the recursive flag was missing)
[#13] Code is not extracted for most projects
cleaned up build output
Installer doesn't work on current debian
added command to export library documentation
Added first draft for a test runner action for ci processes
beatification of the PLCopen XML transformation
fixed problem when devdesc was not installed
optimized execution of codesys and the generated log messages
export documentation as markdown for the source browser
remove debug prints
added script to export library documentation
suppress wine warnings
dont overwrite existing manifests
added script to generate a plain package manifest for a repository
- allow to start the CODESYS IDE with UI "./codesys ide"
add build package action
- updated container to SP15
Home
Home
Home
- prepare IDE to be used in a productive setup
- prepare IDE to be used in a productive setup
uncommended the command ;)
Added xinetd vnc service to start CODESYS.