Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Tommy Murphy
e changing anything in any case. From: kristof.mul...@telenet.be Sent: Monday, January 20, 2020 7:58:25 PM To: Liviu Ionescu Cc: Tommy Murphy ; openocd-devel Subject: Re: [OpenOCD-devel] Compliance with OpenOCD license Hi @Liviu Ionescu, > The scri

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread kristof . mulier
: "Tommy Murphy" , "openocd-devel" Verzonden: Maandag 20 januari 2020 20:46:23 Onderwerp: Re: [OpenOCD-devel] Compliance with OpenOCD license > On 20 Jan 2020, at 21:36, kristof.mul...@telenet.be wrote: > > ... I conclude this particular OpenOCD executable was built

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Liviu Ionescu
> 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

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread kristof . mulier
rphy" , "openocd-devel" Verzonden: Maandag 20 januari 2020 20:18:11 Onderwerp: Re: [OpenOCD-devel] Compliance with OpenOCD license > On 20 Jan 2020, at 21:09, kristof.mul...@telenet.be wrote: > > Waw, that is marvellous. > Thank you very much @Liviu Ionescu You're

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Liviu Ionescu

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Liviu Ionescu
> 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

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread kristof . mulier
- Van: "Liviu Ionescu" Aan: "Tommy Murphy" Cc: "kristof mulier" , "openocd-devel" Verzonden: Maandag 20 januari 2020 19:52:45 Onderwerp: Re: [OpenOCD-devel] Compliance with OpenOCD license > On 20 Jan 2020, at 20:43, Tommy Murphy wrote: >

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Liviu Ionescu
> 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

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Tommy Murphy
compiling for Windows and for compiling for Linux. From: Liviu Ionescu Sent: Monday 20 January 2020 18:39 To: kristof.mul...@telenet.be Cc: Tommy Murphy ; openocd-devel Subject: Re: [OpenOCD-devel] Compliance with OpenOCD license > On 20 Jan 2

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread kristof . mulier
d/ ] Hope this helps. From: kristof.mul...@telenet.be Sent: Monday 20 January 2020 17:41 To: openocd-devel Subject: [OpenOCD-devel] Compliance with OpenOCD license Dear OpenOCD developers, We're building a new IDE for microcontrollers (see https://embeetle.com). Our IDE uses OpenOCD to fla

Re: [OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread Tommy Murphy
ope this helps. From: kristof.mul...@telenet.be Sent: Monday 20 January 2020 17:41 To: openocd-devel Subject: [OpenOCD-devel] Compliance with OpenOCD license Dear OpenOCD developers, We're building a new IDE for microcontrollers (see https://embeetle.com). Our

[OpenOCD-devel] Compliance with OpenOCD license

2020-01-20 Thread kristof . mulier
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/