On 2010-11-12 11:36, Steve Bennett wrote:
[snip lots of detail about building]
I think all this misses the point that *right now* people are trying
to build openocd from git and failing. This means there is a problem
which needs to be fixed. I don't think telling people to go create
(.e.g.) cygwin projects to solve their problem is going to be popular.
I'm no expert in these areas, but for me implementing a mechanism that
is used by gcc would be the best solution, and I think that many will
agree, as such ideas were spoken already.
This mechanism allows to use 3 options:
1. No parameter specified, no jumtcl directory in OpenOCD source tree =>
use jimtcl library that is installed in the system
2. No parameter specified, jimtcl directory present in OpenOCD source
tree => build jimtcl before OpenOCD, use the library in OpenOCD
3. Path to jimtcl library specified => use it in OpenOCD.
That's the way gcc handles dependancies like MPFR, GMP, PPL, etc. (or at
least I think it does it this way [; )
4\/3!!
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
