> On 13 May 2019, at 12:28, <kristof.mul...@telenet.be> > <kristof.mul...@telenet.be> wrote: > > ... the OpenOCD compilation into a standalone Windows executable happens in > Msys2 on Windows. So no need to install Linux or a virtual Linux machine on > your computer.
you no longer need kludges like Msys2, the modern approach is to use Windows System for Linux (WSL), from Microsoft. the WSL2, announced for June, will include a full Linux kernel, tightly coupled with the Windows NT kernel. > Do you think your scripts would run in Msys2 - perhaps with some tweaks? I already tweaked my QEMU build script to run on WSL, so I guess the OpenOCD script can also be tweaked in a similar manner. unfortunately I currently have no resources to do this. > The reason I'm interested in building OpenOCD has everything to do with the > startup I'm working in: > https://embedoffice.com/ > If you have time to check out our website, please let us know what you think > about our initiative 😊 I don't know, I agree that Eclipse is very complicated and inconsistent, and personally I think it is on the down slope, and cannot recommend it for medium/long term developments. if you can make your IDE portable and functional on Windows/Linux/macOS, and base it on an open source extensible architecture, allowing 3rd parties to easily add functionality, it might work. however, if I would have to bet, I would bet on Visual Studio Code. actually I plan to rewrite the GNU MCU Eclipse plug-ins as extensions for VSCode, including the OpenOCD debug plug-in. regards, Liviu _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel