On Mon, Jan 20, 2020 at 12:29 AM Andreas Fritiofson <
andreas.fritiof...@gmail.com> wrote:
>
>
> On Fri, Jan 17, 2020 at 4:24 PM Antonio Borneo
> wrote:
>
>> On Fri, Jan 17, 2020 at 3:37 PM Oleksij Rempel
>> wrote:
>> >
>> > Am 17.01.20 um 12:45 schrieb Antonio Borneo:
>> is there any method to
The instructions definitely work on Ubuntu.
I've been using Ubuntu 18 lately.
Other distros probably work as well.
Don't forget to read the "prerequisite" instructions for installing docker.
Once that's done it should be trivial to pull and run the build process.
As I mentioned earlier if you want
Hi @Liviu Ionescu,
> The scripts have lots of configuration environment
> variables, if you want to build a more recent version,
> you need to tweak them.
> [..]
Uh oh...
I have not even the foggiest idea how to "tweak" your
build scripts.
To be honest, I was hoping to simply run the build script
> On 20 Jan 2020, at 21:36, kristof.mul...@telenet.be wrote:
>
> ... I conclude this particular OpenOCD executable was built last summer.
That's correct.
Since OpenOCD has no release schedule, I have no idea when to make xPack
releases.
> .. I suppose your
> instructions to build the OpenO
Thank you @Liviu Ionescu,
I just downloaded an xPack from
https://github.com/xpack-dev-tools/openocd-xpack/releases
and behold, there are Windows binaries inside! I run the OpenOCD executable and
it prints:
$ xPack OpenOCD, 64-bit Open On-Chip Debugger 0.10.0+dev (2019-07-17-11:28)
$ Lice
> On 20 Jan 2020, at 20:43, Tommy Murphy wrote:
>
> Over the years Liviu's approach is by far the simplest that I have come
> across for cross compiling for Windows and for compiling for Linux.
The build scripts are quite complex, but the point is to generate standalone
binaries the run eff
Waw, that is marvellous.
Thank you very much @Liviu Ionescu
I will try to run the build scripts. The result will be an xPack, right? I've
got no idea what an xPack actually is, but I suppose the Windows binaries for
OpenOCD will be somewhere inside the xPack ;-)
- Oorspronkelijk bericht ---
> On 20 Jan 2020, at 20:26, kristof.mul...@telenet.be wrote:
>
> Thank you @Tommy Murphy,
>
> I noticed that docker is being used. Does this mean that the resulting
> binaries cannot run natively on Windows? Do they need a docker layer to run
> on?
The Windows binaries run natively on Windo
And before anybody asks - no, they don't need Cygwin or any other "subsystem"
either. 🙂
They are completely native Windows binaries cross compiled from Linux using the
Windows/MinGW gcc toolchain.
Over the years Liviu's approach is by far the simplest that I have come across
for cross compiling
Thank you @Tommy Murphy,
I searched on the xpack website and discovered some build instructions here:
https://github.com/xpack-dev-tools/openocd-xpack/blob/xpack/README-BUILD.md
I noticed that docker is being used. Does this mean that the resulting binaries
cannot run natively on Windows? Do
> please help us to find a better way to build OpenOCD for Windows.
On this specific issue I would recommend that you (and anybody else having
issues with building OpenOCD) have a look at Liviu Ionescu's xPack OpenOCD
project and the docker based build scripts that he provides for (cross)
build
Dear OpenOCD developers,
We're building a new IDE for microcontrollers (see https://embeetle.com).
Our IDE uses OpenOCD to flash the microcontroller. I compile OpenOCD
for Windows using the guide from Rocco Marco:
https://www.playembedded.org/blog/building-openocd-under-windows-using-msys2/
On Fri, Jan 17, 2020 at 4:24 PM Antonio Borneo
wrote:
> On Fri, Jan 17, 2020 at 3:37 PM Oleksij Rempel
> wrote:
> >
> > Am 17.01.20 um 12:45 schrieb Antonio Borneo:
> is there any method to force jenkins to rebuild a patch before merging
> it? Maybe has to be rebased on top of master.
>
>
I don'
14 matches
Mail list logo
