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'
to achieve just that.

Is that correct?

Kind regards,
Kristof

----- Oorspronkelijk bericht -----
Van: "Liviu Ionescu" <i...@livius.net>
Aan: "kristof mulier" <kristof.mul...@telenet.be>
Cc: "Tommy Murphy" <tommy_mur...@hotmail.com>, "johan" <jo...@embeetle.com>, 
"matic" <ma...@embeetle.com>, "openocd-devel" 
<openocd-devel@lists.sourceforge.net>
Verzonden: Zaterdag 29 augustus 2020 19:59:41
Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build.

> 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-xpack/raw/xpack/scripts/git-clone.sh 
| bash
$ sudo rm -rf ~/Work/openocd-*
$ bash ~/Downloads/openocd-xpack.git/scripts/build.sh --linux64

$ '/home/ilg/Work/openocd-0.10.0-14/linux-x64/install/openocd/bin/openocd' 
--version
xPack OpenOCD, x86_64 Open On-Chip Debugger 0.10.0+dev (2020-08-29-17:49)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html


I doubt that it can be anything simpler than this. 

And, to quote a company with a fruit logo, "it just works".

Regards,

Liviu


_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to