Hello, It remains somewhat unclear to me exactly how badly distributors need to see a solution today, when users (who are all developers, right?) should be able to compile the code themselves and use the FTD2XX driver.
If Windows is the blocker, the first question that should be answered is: how do we build OpenOCD on Windows? Everything else goes from that. Thus, can someone explain why this cannot be solved by good build process documentation? No code, other than some command line examples. Just a good old fashioned HOWTO for building the MinGW32 distribution from scratch. Do we have these today in the tree? I cannot trivially locate them.... Why not? Same for CygWin, and I apologize if I missed either of these in-tree. If someone were to provide instructions for the setup steps (in-tree), someone can probably turn that into a build-kit script (in-tree). And someone else might be able to integrate that with the Qt helper already under development (which will be in-tree). Hurrah! Clarifying this somewhat, the required build process seems to be: 1) download(/compile)/install a MinGW32 toolchain 2) compile/install OpenOCD dependencies in temporary dir 3) this step intentionally left empty, because... I believe the last step (compile/install OpenOCD) will already be handled by the Qt wrapper, but I hope interested developers will work on the list to clarify these details. Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
