Closed UlfBj closed 9 months ago
Current instructions to generate the tree binary involves cloning the VSS repo. Is there a branch with these changes pushed to the VSS repo ?
The changes was done at the Vss-tools quite some time ago, so it has migrated to vss. The reason vissv2 had not followed until now was a replace statement in go.mod
On Fri, Dec 22, 2023, 09:11 PeterW @.***> wrote:
Current instructions to generate the tree binary involves cloning the VSS repo. Is there a branch with these changes pushed to the VSS repo ?
— Reply to this email directly, view it on GitHub https://github.com/w3c/automotive-viss2/pull/95#issuecomment-1867371178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJERQQOX4E6SARLLULGKSXTYKU6EZAVCNFSM6AAAAABA6NZMRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXGM3TCMJXHA . You are receiving this because you authored the thread.Message ID: @.***>
Ok, verified the generation of the binary file. Some corrections needed in the readme instructions for the instructions in the readme will. pull request on its way in vss-tools.
@petervolvowinz, and everyone else using this server: Please observe that this PR requires that the binary file containing the VSS tree is regenerated (make binary) as there is an update of the tree parser.