Ticket #12: Accessing libraries, the example and the unittest for SP16.10
co⚡e: Sparkplug™ MQTT edge and host
questions
(Ticket)
Binaries tree [f9106e] TAG 16.10 For users who wish to use the library with older runtimes, the libraries, the example and the unittest are available for SP16.10. We have confirmed these versions to run correctly. To get this version, install git for windows and run this command: git clone -b 16.10 https://forge.codesys.com/git/lib,cobolt,binaries.git/ . Or you can visit the Tag 16.10 and download them from your browser. The binaries could in theory be used in SP15.x but since we have NOT tested this, your mileage may vary! If you want to Try this, you still need a SP16.10 IDE and set the compiler for SP16.10 and download this version into a SP15 runtime. Warning, please read this! We decided we will not develop for SP16.x anymore. Current development will continue in SP18! See Ticket [#158] for further details. 2022-04-17 20:09:24.018000 Ticket #12: Accessing libraries, the example and the unittest for SP16.10 co⚡e: Sparkplug™ MQTT edge and host cobolt tickets questions False /lib/cobolt/questions/12/ Ticket [f9106e] TAG 16.10 Accessing libraries, the example and the unittest for SP16.10 False 3 2022-04-17 20:03:06.077000 12 Accessing libraries, the example and the unittest for SP16.10 open Binaries tree [f9106e] TAG 16.10 For users who wish to use the library with older runtimes, the libraries, the example and the unittest are available for SP16.10. We have confirmed these versions to run correctly. To get this version, install git for windows and run this command: git clone -b 16.10 https://forge.codesys.com/git/lib,cobolt,binaries.git/ . Or you can visit the Tag 16.10 and download them from your browser. The binaries could in theory be used in SP15.x but since we have NOT tested this, your mileage may vary! If you want to Try this, you still need a SP16.10 IDE and set the compiler for SP16.10 and download this version into a SP15 runtime. Warning, please read this! We decided we will not develop for SP16.x anymore. Current development will continue in SP18! See Ticket [#158] for further details. False False 0 0 0 None hermsen hermsen
Last updated: 2022-04-17
Post by hermsen on #158 Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -17,7 +17,7 @@ Tasks for old version: * :point_right: CODESYS git *ONLY* supports SP17 and later:exclamation: -* [ ] Create a commit in the binaries git, which stores the libraries and projects which can be opened using SP16 Patch 1 development environment. The libraries should compile and be installed in the repository, the unit test should run, the project should run and send data to/from Edge and Host. +* [x] Create a commit in the binaries git, which stores the libraries and projects which can be opened using SP16 Patch 1 development environment. The libraries should compile and be installed in the repository, the unit test should run, the project should run and send data to/from Edge and Host. * [x] Host * [x] Stack * [x] Edge
Last updated: 2022-04-17
Post by hermsen on #158 Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -24,7 +24,7 @@ * [x] Example * [x] Unittest * [x] Create a git tag of that SP16.10 commit. -* [ ] Create instructions for how to access that for users who want to use an older version in the FAQ. +* [x] Create instructions for how to access that for users who want to use an older version in the FAQ. Tasks for SP18 version:
Last updated: 2022-04-17
(no subject)
co⚡e: Sparkplug™ MQTT edge and host
questions
(Thread)
Last updated: 2022-04-17
Post by hermsen on #12 Accessing libraries, the example and the unittest for SP16.10
co⚡e: Sparkplug™ MQTT edge and host
questions
(Post)
assigned_to: h-hermsen --> nobody
Last updated: 2022-04-17
Post by hermsen on #158 Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -28,12 +28,12 @@ Tasks for SP18 version: -* [ ] Use SP18 to checkout, close project, open project, and commit the SP18 changes with a commit message containing this Ticket number and title -* [ ] Up the compiler version to SP18 -* [ ] Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" -* [ ] Commit and push to main +* [x] Use SP18 to checkout, close project, open project, and commit the SP18 changes with a commit message containing this Ticket number and title +* [x] Up the compiler version to SP18 +* [x] Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" +* [x] Commit and push to main * [x] Host v1.4.0.0 * [x] Stack v1.5.0.0 - * [ ] Edge - * [ ] Example - * [ ] Unittest + * [x] Edge + * [x] Example + * [x] Unittest
Last updated: 2022-04-17
Post by i-campbell on #158 Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -32,7 +32,7 @@ * [ ] Up the compiler version to SP18 * [ ] Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" * [ ] Commit and push to main - * [ ] Host + * [x] Host v1.4.0.0 * [x] Stack v1.5.0.0 * [ ] Edge * [ ] Example
Last updated: 2022-04-17
Post by hermsen on #158 Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: accepted --> closed
Last updated: 2022-04-17
Ticket #158: Migrate to SP18 Development Environment and SP18 Compiler
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Ticket)
We intend eventually to use some SP18 compiler features, namely UTF8 strings, which will bring processing performance enhancements as well as application memory usage improvements. Also, we want to use SP18 development environment. This would mean though that for end users to use the latest version of co⚡e, they will need to use SP18 development environment and SP18 compiler, even if with their older runtimes. The only problem here would be, those with devices from manufacturers which both: a) only work with their own customized version of the CODESYS development environment and b) are not yet at SP18 with that development environment (eg. has released SP17 a month ago) So we have two options moving forward. Option 1 - We create a release of the current state, and for anyone not using the SP18 development environment yet, they have to use this version. All versions from now will require SP18. Option 2 - We try to continue development in such a way that allows for the old compiler also. Option 2 is more work than Option 1, but we understand some people might take time to move to SP18. We opt for Option 1, as this will let us realize the new performance improvements faster. Tasks for old version: 👉 CODESYS git ONLY supports SP17 and later❗ Create a commit in the binaries git, which stores the libraries and projects which can be opened using SP16 Patch 1 development environment. The libraries should compile and be installed in the repository, the unit test should run, the project should run and send data to/from Edge and Host. Host Stack Edge Example Unittest Create a git tag of that SP16.10 commit. Create instructions for how to access that for users who want to use an older version in the FAQ. Tasks for SP18 version: Use SP18 to checkout, close project, open project, and commit the SP18 changes with a commit message containing this Ticket number and title Up the compiler version to SP18 Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" Commit and push to main Host v1.4.0.0 Stack v1.5.0.0 Edge Example Unittest2022-04-17 21:56:42.562000 Ticket #158: Migrate to SP18 Development Environment and SP18 Compiler co⚡e: Sparkplug™ MQTT edge and host cobolt tickets tickets False /lib/cobolt/tickets/158/ Ticket Migrate to SP18 Development Environment and SP18 Compiler False 13 2022-04-08 21:37:12.901000 158 Migrate to SP18 Development Environment and SP18 Compiler closed We intend eventually to use some SP18 compiler features, namely UTF8 strings, which will bring processing performance enhancements as well as application memory usage improvements. Also, we want to use SP18 development environment. This would mean though that for end users to use the latest version of co⚡e, they will need to use SP18 development environment and SP18 compiler, even if with their older runtimes. The only problem here would be, those with devices from manufacturers which both: a) only work with their own customized version of the CODESYS development environment and b) are not yet at SP18 with that development environment (eg. has released SP17 a month ago) So we have two options moving forward. Option 1 - We create a release of the current state, and for anyone not using the SP18 development environment yet, they have to use this version. All versions from now will require SP18. Option 2 - We try to continue development in such a way that allows for the old compiler also. Option 2 is more work than Option 1, but we understand some people might take time to move to SP18. We opt for Option 1, as this will let us realize the new performance improvements faster. Tasks for old version: 👉 CODESYS git ONLY supports SP17 and later❗ Create a commit in the binaries git, which stores the libraries and projects which can be opened using SP16 Patch 1 development environment. The libraries should compile and be installed in the repository, the unit test should run, the project should run and send data to/from Edge and Host. Host Stack Edge Example Unittest Create a git tag of that SP16.10 commit. Create instructions for how to access that for users who want to use an older version in the FAQ. Tasks for SP18 version: Use SP18 to checkout, close project, open project, and commit the SP18 changes with a commit message containing this Ticket number and title Up the compiler version to SP18 Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" Commit and push to main Host v1.4.0.0 Stack v1.5.0.0 Edge Example Unittest False False 0 0 0 None 2.0.0.0: SparkplugB Primary Node i-campbell hermsen
Last updated: 2022-04-17
Post by hermsen on #152 add yml pipeline
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1 +1,10 @@ -Add a yml file to auto build various artefacts +Add a yml file to auto build various artefacts; + +* [x] binaries +* [x] project +* [x] unittest +* [ ] co⚡e-edge.library +* [ ] co⚡e-host.library +* [ ] co⚡e-stack.library + +Suggestion: only add a .yml pipeline to binaries git in order to build and package tags.
Last updated: 2022-04-17
Ticket #152: add yml pipeline
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Ticket)
Add a yml file to auto build various artefacts; binaries project unittest co⚡e-edge.library co⚡e-host.library co⚡e-stack.library Suggestion: only add a .yml pipeline to binaries git in order to build and package tags.2022-04-17 22:09:17.738000 Ticket #152: add yml pipeline co⚡e: Sparkplug™ MQTT edge and host cobolt tickets tickets False /lib/cobolt/tickets/152/ Ticket add yml pipeline False 4 2022-01-09 12:01:16.695000 152 add yml pipeline open Add a yml file to auto build various artefacts; binaries project unittest co⚡e-edge.library co⚡e-host.library co⚡e-stack.library Suggestion: only add a .yml pipeline to binaries git in order to build and package tags. False False 0 0 0 None 2.0.0.0 Standard Feature Product (SFP) hermsen hermsen
Last updated: 2022-04-17
(no subject)
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Thread)
Last updated: 2022-04-17
Home
botinok
wiki
(WikiPage)
This is the personal project of botinok. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-04-19
Home
yehudabd
wiki
(WikiPage)
This is the personal project of yehudabd. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-04-19
wiki Discussion
yehudabd
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-04-19
blog Discussion
yehudabd
blog
(Discussion)
Forum for blog comments
Last updated: 2022-04-19
(no subject)
yehudabd
wiki
(Thread)
Last updated: 2022-04-19
Home
eeyrsja
wiki
(WikiPage)
This is the personal project of eeyrsja. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-04-20
wiki Discussion
eeyrsja
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-04-20
blog Discussion
eeyrsja
blog
(Discussion)
Forum for blog comments
Last updated: 2022-04-20
(no subject)
eeyrsja
wiki
(Thread)
Last updated: 2022-04-20
Home
connyt
wiki
(WikiPage)
This is the personal project of connyt. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-04-20
wiki Discussion
connyt
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-04-20
blog Discussion
connyt
blog
(Discussion)
Forum for blog comments
Last updated: 2022-04-20
(no subject)
connyt
wiki
(Thread)
Last updated: 2022-04-20