Hi Dick, On Wed, Apr 29, 2009 at 16:47, Dick Hollenbeck <[email protected]> wrote: > Please always state your build environment. What operating system, and what > tool chain is it trying to use? > > mingw32? > cygwin?
Just Visual Studio 2005, but I guess the exact version does not matter much. > I will assume windows in the discussion below: > > Then be aware of my remarks that it has not been tested on Windows. There > is some massaging required. It would only take about an hour to get it to > work on windows, but my Windows days are mostly over. As I said, the makefile generation mostly works "out of box" (I only had to specifty location of libftd2xx manually). Right now I'm trying nmake makefiles, not VS projects. > To deal with your issues, and assuming Windows, I would stick with the GNU > compiler as your first attempt, and this means Mingw. So when generating > your make files, be sure and use the command line option with tells it to > use Mingw, not MS VC. Also make sure all your toolchain commands are in > your path, including svn client and gcc. I know that it can be compiled with mingw and have done it myself. What I'm interested in now is making a pure msvc build, with no Unix-specific headers and libraries. But this means getting rid of all C99 and GNU stuff (besides what can be fixes with #defines, like __attribute__). Is that something that can be considered for OpenOCD at all, or completely out of question? The changes required so far are not really substantial, if a bit tedious to do. -- WBR, Igor _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
