A more general question: what is the reason for integrating jimtcl as a submodule in the first place? According to repology it seems to be widespread. We deprecated the libjaylink submodule, what is the reason to keep jimtcl?
Best regards, Marc On Fri, 2024-06-21 at 14:31 +0200, Antonio Borneo wrote: > You can try this, on a clean clone, simulating that it was an old > clone on which you suddenly run an update: > > git clone https://github.com/openocd-org/openocd > cd openocd > git checkout v0.10.0 -- .gitmodules > ./bootstrap > > It will fail because it cannot get access to the jimtcl required by > current OpenOCD in the repo specified by v0.10.0. > > git checkout HEAD -- .gitmodules > ./bootstrap > > It will still fail because the git repo of the submodules has been > already set incorrectly from the first run of bootstrap and does not > get updated. > > Edit bootstrap to add the line 'git submodule sync' between 'git > submodule init' and 'git submodule update' > > ./bootstrap > > now it will succeed! > > > Karl, > I will send the patch on gerrit with your email as reported-by. > > But as you are an active user of OpenOCD, it would be nice if you > give another try to install an openid for any further contribution or > to review the patches in gerrit. > > Regards, > Antonio >
