While this works with all other textual languages, with the VIs this is not possible, Git just creates another copy of the VI on every modification, and so on, and so on….
The SCCs always tries to minimize disk footprint of the source code by working on Deltas, which is difference of the subsequent codes, where the last version is nothing but a bunch of differences from the original file. Libraries, Projects and Classes are XML format, but they are eventually holding some binary data inside. One of the main disadvantages of LV is the binary proprietary format of the VIs, which hold the real source code. The history with LabVIEW with Source Code Control Systems hasn’t been flowers. I had a workable solution, but it was far from being a good one, but until we get to the topic of a possible solution, let’s recap some things. One of the things is that I didn’t have a good solution for it. What about a git based manager for your source code, zip files, binaries (PPLs), etc…?įor a while I’ve been trying to write this post, but several reasons kept me from finishing the write.
0 kommentar(er)
