> 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 repo). So what would change in these commands to achieve that? I refer to the commands you posted in your previous mail: $ 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 Is it the trick with the '~/Downloads/openocd-xpack.git/scripts/defs-source.sh' file (uncommenting the last three lines)? Or is it something else? My sincere apologies for the hassle. I appreciate your help so much! 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 20:11:21 Onderwerp: Re: [OpenOCD-devel] Missing libusb shared object file in xPack build. > 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, you can start experimenting with any other commit, the build scripts do not care what content they build. Liviu _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
