You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrating with the CAN based virtual terminal would be a huge feature. It would allow us to communicate with the operator and allow for much better debugging on machine. If we are going to give back to the farmers who allow us to host our machines by providing them with additional functionality to their machines this will be critical
Based on my call with @wang701 we will need to download the ISOAgLib library and compile that with whatever VT code we write ourselves using cmake. Since this is compiled code, a two stage build is appropriate: build the code on the first container and then move the binary and dynamically linked libraries over to the slimmed runner container. There does not appear to be many dependencies beyond the ISOAgLib stuff
Potential issues:
ISOAgLib Is currently going a transition as they are being purchased. Their website and other things are not stable and may cause issues with us programmatically downloading the library as things are moved around or no longer available. Will we want to host our own mirror of the library version that we use?
This will require a connection to socketcan. Will this require running in host mode?
What base container should we use? This uses cmake extensively, but there is not a dedicated cmake docker base container, we could use gcc for the builder (if that helps?) or just debian-buster
Can we test this or programmatically verify that the container is running properly?
The text was updated successfully, but these errors were encountered:
Based on 10/27/20 call with @wang701.
Integrating with the CAN based virtual terminal would be a huge feature. It would allow us to communicate with the operator and allow for much better debugging on machine. If we are going to give back to the farmers who allow us to host our machines by providing them with additional functionality to their machines this will be critical
Based on my call with @wang701 we will need to download the ISOAgLib library and compile that with whatever VT code we write ourselves using cmake. Since this is compiled code, a two stage build is appropriate: build the code on the first container and then move the binary and dynamically linked libraries over to the slimmed runner container. There does not appear to be many dependencies beyond the ISOAgLib stuff
Potential issues:
debian-buster
The text was updated successfully, but these errors were encountered: