On 09/11/2010, at 5:02 PM, Øyvind Harboe wrote: > On Tue, Nov 9, 2010 at 12:07 AM, Steve Bennett <[email protected]> wrote: >> 1. The current openocd doesn't build on cygwin >> 2. The multi-step configure/install/build is inconvenient. >> >> The attached patch addresses these by configuring, building >> and using jimtcl in-place. >> >> Note that it should still be possible to use an installed jimtcl >> if required by overriding CPPFLAGS and LDFLAGS but I >> haven't tried it. > > Would that be robust? What if there is a file in the in-place jim-tcl > that isn't in the installed folder. Wouldn't OpenOCD then find the > file it shouldn't? > > I'd like to see a configure time option in openocd to choose between > using currently installed and building in-place.
I think that's the best option too. I think I mentioned it before, something like --with-jim-tcl=<path> as an option, but using the in-place version if not specified. But this is beyond my automake skills. Someone else will need to do it. (And I don't think Peter likes this option). > > > BTW, I very much appreciate that you patch and contribution on > the discussion here! This is most useful input, even if we're going > a few extra rounds to get this patch to cover every case. I don't > expect you to take it across the finish line as there are many > on the list with opinions about this topic. That's fine. openocd is a major user of Jim Tcl. I don't want anyone to feel that the new version is a step backwards because of some minor build issues. -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: 0434 921 300 E: [email protected] F: 07 3102 9221 _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
