Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Tommy Murphy
Liviu's scripts build his snapshot sources. If you want to build from the openocd repo then uncomment the three lines here: https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/scripts/defs-source.sh#L41 FWIW here are all of the commands that I run (all itemised in Liviu's instructions) t

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 21:18, kristof.mul...@telenet.be wrote: > > ... I got it running properly told you so! > So what would change in these commands to achieve that? ... defs-source.sh' > file (uncommenting the last three lines)? Or is it something else? Keine Ahnung, I never used the script

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
> Once you have this running properly, > you can start experimenting with any > other commit, the build scripts do not > care what content they build. I got it running properly - so I feel entitled now to start experimenting with another commit (preferably the master branch of the official OpenOCD

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 21:06, kristof.mul...@telenet.be wrote: > > does this pull the latest > master branch from the official OpenOCD git repo before doing the build? Negative, this is a production build that pulls a specific commit from my openocd fork. Once you have this running properly, y

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
Thanks @Liviu, That's simple indeed! I'm trying it right now. However, I was wondering: does this pull the latest master branch from the official OpenOCD git repo before doing the build? I remember one had to uncomment the last three lines in '~/Downloads/openocd-xpack.git/scripts/defs-source.sh'

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 20:34, kristof.mul...@telenet.be wrote: > > Did you refer to this guide from Liviu: > https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md On a Ubuntu 20 VM, with curl, git and docker installed: $ curl -L https://github.com/xpack-dev-tools/openocd-

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Tommy Murphy
If you follow Liviu's build instructions to the letter everything will build perfectly every time. I've done it many times myself. Once you have his stuff building as is you can experiment with changing the build scripts or sources according to your requirements if necessary. But start first by

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
Hi @Tommy Murphy, Thank you very much. I did not change the build scripts - except for commenting out the last three lines in: ~/Downloads/openocd-xpack.git/scripts / defs-source.sh Commenting out these last three lines enables the pulling of the latest OpenOCD git repo. Did you refer to th

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 19:42, kristof.mul...@telenet.be wrote: > > To keep the development repository in sync with the original OpenOCD > repository, in the xpack-dev-tools/openocd Git repo: The key trick there is 'in the xpack-dev-tools/openocd Git repo'. But this will probably not solve your

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
> The key trick there is 'in the xpack-dev-tools/openocd Git repo'. Right, so I stay in the git repo that I cloned like this: $ curl -L https://github.com/xpack-dev-tools/openocd-xpack/raw/xpack/scripts/git-clone.sh | bash $ cd ~/Downloads/openocd-xpack.git So the "merge from upstream/master"

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
Hi Liviu, I'm indeed experimenting :-) The reason I did those merges is because of this part in your guide (see https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md) Update git repos = To keep the development repository in sync with the original OpenOCD re

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 19:28, kristof.mul...@telenet.be wrote: > > What did I do wrong? For one, you merged different Git repos. This shows that you are far from understanding the build process. :-( > but I > still want to be able to compile OpenOCD from the sources :-) Sure, you're free to e

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
Hi @Liviu, Thank you for your quick reply. I am thankful for the binaries you provide - I really do - but I still want to be able to compile OpenOCD from the sources :-) I didn't change the build scripts. Here are the steps I took. FIRST TRY (29 Aug 2020, morning) ===

Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread Liviu Ionescu
> On 29 Aug 2020, at 16:30, kristof.mul...@telenet.be wrote: > > $ ls -l > total 4816 > -rwxrwx--- 1 root vboxsf 73232 Aug 29 14:14 libftdi1.so.2.4.0 > -rwxrwx--- 1 root vboxsf 22840 Aug 29 14:14 libhidapi-hidraw.so.0.0.0 > -rwxrwx--- 1 root vboxsf 992288 Aug 29 1

[OpenOCD-devel] Missing libusb shared object file in xPack build.

2020-08-29 Thread kristof . mulier
Hi Liviu (and other OpenOCD developers), I just completed another build of OpenOCD on my Ubuntu VM. I'm following the XPack guide from @Liviu Ionescu, see: [ https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md | https://github.com/xpack-dev-tools/openocd-xpack/blob/xpac