This is an automated email from Gerrit.
Christopher Head (ch...@zaber.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/5406
-- gerrit
commit 1a984a8e80ba60d5f83b44dc5e7e0c930045b27e
Author: Christopher Head
Date: Tue Jan 21 12:44:46 2020 -0800
Is some or all of the OpenOCD development actually done on the zylin repo?
All the emails that I get about commits seem to relate to that.
Or is that just for reviewing commits before the are accepted to the master
openocd repo?
http://openocd.zylin.com/#/c/5405/
I find it all a bit confusing to
> On 21 Jan 2020, at 20:36, Tommy Murphy wrote:
>
> ... Maybe all development IS done on the master branch?
I guess so, I can't find a separate branch in the official repo.
Regards,
Liviu
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourc
> As I mentioned before, the resulting archives are tagged with a version
> number specific to the xPack release.
Ok - so you mean the archive name itself as opposed to the version details
which the openocd executable outputs which seems to be the generic openocd one
as I mentioned before?
And,
Hi @Liviu,
Thank you for reminding us.
I promise I won't distribute them with these names.
I will certainly not push them to the xPack repos.
Kind greetings,
Kristof
- Oorspronkelijk bericht -
Van: "Liviu Ionescu"
Aan: "kristof mulier"
Cc: "Tommy Murphy" , "openocd-devel"
Verzonden:
Actually if you want really bleeding edge stuff then you might want to build
from whatever the development branch is instead of master.
I'm not sure how this is managed in the OpenOCD project though.
Maybe all development IS done on the master branch?
Maybe somebody else can comment?
OPENOCD_GIT_
> On 21 Jan 2020, at 20:23, kristof.mul...@telenet.be wrote:
>
> and unzipped xpack-openocd-0.10.0-14-win32-x64.zip.
As I mentioned before, the resulting archives are tagged with a version number
specific to the xPack release.
I guess there are also some files inside the archive which menti
Thanks!!
You and Liviu made my day :D
Van: "Tommy Murphy"
Aan: "kristof mulier" , "Liviu Ionescu"
Cc: "openocd-devel"
Verzonden: Dinsdag 21 januari 2020 19:28:01
Onderwerp: Re: Building OpenOCD xPack
> The build was successful!
Great.
The whole process is easier than I probably mad
> The build was successful!
Great.
The whole process is easier than I probably made it seem! 🙂
Just follow Liviu's instructions and then edit the scripts/defs-source.sh file.
In fact Liviu just accepted a Pull Request from me that adds the required
defines commented out so they just need to be un
Hi @Tommy Murphy and @Liviu Ionescu,
The build was successful!
I transferred the build outputs to Windows 10 and unzipped
xpack-openocd-0.10.0-14-win32-x64.zip . Then I run openocd.exe :
C:\Users\Kristof\ubuntu_shared\xpack-openocd-0.10.0-14-win32-x64\xpack-openocd-0.10.0-14\bin
> openocd.e
This is an automated email from Gerrit.
Antonio Borneo (borneo.anto...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/5405
-- gerrit
commit 30b55abf809750a1157bf52a8f6fbb422a020e79
Author: Antonio Borneo
Date: Wed Oct 2 18:21:05 2019 +0200
if you don't use the curl command then you need to do the two commands listed
on the instructions page:
$ rm -rf ~/Downloads/openocd-xpack.git
$ git clone --recurse-submodules
https://github.com/xpack-dev-tools/openocd-xpack.git \
~/Downloads/openocd-xpack.git
the other stuff is about using th
Hi @Tommy Murphy,
I did not issue the command:
$ curl -L
https://github.com/xpack-dev-tools/openocd-xpack/raw/xpack/scripts/git-clone.sh
| bash
But I issued the following commands instead:
$ rm -rf ~/Downloads/openocd-xpack.git
$ git clone --recurse-submodules --branch xpack-develop
htt
> The folder ~/Downloads/openocd-xpack.git/scripts does not contain a file
> defs-source.sh:
Are you sure that you did this to retrieve them?
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md
$ curl -L
https://github.com/xpack-dev-tools/openocd-xpack/raw/xpack/script
Hi @Liviu Ionescu,
I found the new donate button on the xPack website, and I've
just donated €60.
Kind greetings,
Kristof
- Oorspronkelijk bericht -
Van: "Liviu Ionescu"
Aan: "kristof mulier"
Verzonden: Dinsdag 21 januari 2020 17:20:32
Onderwerp: Re: Thank you for xPack
> On 21 Jan 20
Hi @Tommy Murphy,
The folder ~/Downloads/openocd-xpack.git/scripts does not contain a file
defs-source.sh :
$ cd ~/Downloads/openocd-xpack.git/scripts
$ ls --all
. .. helper
$ cd helper
$ ls --all
. .. common-functions-source.sh
container-functions-source.sh
.git host-functions-source.
> Please be aware that the resulted binaries are still tagged with the xPack
> version, although the content is different.
Actually it's not because the xPack specific --enable-branding="xPack OpenOCD
..." passed to configure is quietly ignored. 🙂
Open On-Chip Debugger 0.10.0+dev-01032-gf980995
> On 21 Jan 2020, at 18:42, Tommy Murphy wrote:
>
> FWIW this worked for me to use Liviu's xPack Project OpenOCD build scripts to
> build from the upstream master repo instead of Liviu's repos/snapshots...
> edit defs-source.h ...
Aha. Good to know.
Please be aware that the resulted binari
> On 21 Jan 2020, at 18:44, Tommy Murphy wrote:
>
> you cannot omit the commit expecting the script to default to the latest.
If you want the very latest HEAD, can you pass HEAD instead of the id?
Liviu
___
OpenOCD-devel mailing list
OpenOCD-de
Sorry - obviously change the URL, beanch and/or commit as necessary.
I just used the latest mirror repo, master branch and latest commit in this
example.
At the moment you MUST provide ALL of these - e.g. you cannot omit the commit
expecting the script to default to the latest.
__
FWIW this worked for me to use Liviu's xPack Project OpenOCD build scripts to
build from the upstream master repo instead of Liviu's repos/snapshots...
Edit your local copy of ~/Downloads/openocd-xpack.git/scripts/defs-source.sh
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/scripts
As I said I would not try to merge Liviu's repo with upstream just yet.
In any case the scripts will try to pull his stuff anew anyway while building.
It won't use anything local.
Did you pipeclean the standard xPack build process as I asked?
From: kristof.mul...@te
> On 21 Jan 2020, at 17:43, Tommy Murphy wrote:
>
> I don't think that trying to merge Liviu's openocd forked repo with the
> master/upstream repo is going to work (easily).
> But I've never tried it.
If I remember right, most of the times it worked without conflicts.
Regards,
Liviu
__
Hi @Tommy Murphy and @Liviu Ionescu,
I've tried some more things to get the merge done.
Here is what I tried:
# Navigate to the git repo
#
$ cd ~ /Downloads/openocd -xpack.git
# Checkout the master
# ---
$ git checkout master
warning: unable to r
Did you first pipeclean the standard xPack build process by just running the
script that pulls the build scripts and then running, say,
bash ~/Downloads/xpack-openocd-build/scripts/build.sh --win64
Just to make sure that that works?
I was going to separately try to configure the scripts to buil
My apologies to bother you guys again,
But I got stuck once more.
I successfully completed the prerequisites (see
https://xpack.github.io/xbb/prerequisites/)
so I can start updating the git repos (see "How to build distributions" in the
guide
at
https://github.com/xpack-dev-tools/openocd-xp
No problem Kristof.
All the kudos goes to Liviu though for developing the scripts.
I just use them! ?
From: kristof.mul...@telenet.be
Sent: Tuesday 21 January 2020 15:10
To: Tommy Murphy
Cc: Liviu Ionescu ; openocd-devel
Subject: Re: Building OpenOCD xPack
Than
Thank you @Tommy Murphy.
I thought it would be this way, but I'm happy to get it confirmed.
Basically I'm a hardware guy (PCB design, ...) who's also getting
involved into software design in the past few years.
I'm very thankful to people like you (@Tommy Murphy) and @Liviu
Ionescu, for helpi
Great - another thing to note in case it was not clear - even when running on,
say, Ubuntu 19.10 the xPack stuff builds under an older Linux (CentOS 6 I
think) docker image with a newer than default compiler resulting in Linux
executables that run on a wider set of distros/versions than if built
Thank you @Tommy Murphy!
I will proceed with the workaround you proposed :D
Van: "Tommy Murphy"
Aan: "kristof mulier"
Cc: "Liviu Ionescu" , "openocd-devel"
Verzonden: Dinsdag 21 januari 2020 15:50:24
Onderwerp: Re: Building OpenOCD xPack
That issue is unfortunate but is ultimately a p
That issue is unfortunate but is ultimately a problem at the docker repo end.
The workaround here worked for me to get docker installed:
https://github.com/docker/for-linux/issues/833#issuecomment-544236041
However when adding the user to the docker group I always found that I had to
reboot rath
I tried Ubuntu 19.10 and get the same error as Kristof.
Looks like a problem with the docker repos:
https://github.com/docker/for-linux/issues/833
There's a workaround in that issue.
I generally try to stick to LTS versions for production work.
Hope this helps
Cheers
Tommy
Hi Kristof
I just followed the prerequisites installation instructions to install docker
on a clean Ubuntu 18 virtual machine and it all worked fine for me.
See attached.
Cheers
Tommy
From: kristof.mul...@telenet.be
Sent: Tuesday 21 January 2020 11:56
To: Tommy
Hi @Liviu,
Hi @Tommy,
I'm following the guide(s) on the xPack website. However, I got stuck when
executing
the fourth command on the Prerequisites page (see
https://xpack.github.io/xbb/prerequisites/):
$ sudo add-apt-repository "deb [arch=amd64]
https://download.docker.com/linux/ubuntu $( l
34 matches
Mail list logo
