On Tue, 2009-12-01 at 21:08 -0800, Zach Welch wrote: > Hi all, > > Assuming a split between policy and mechanism can be addressed, OpenOCD > will become much more usable as a proper library. One of the questions > that needs resolution is "how to install our header files". The answer > that we chose for this will determine how much restructuring will be > required to make it happen. > > The easiest option to simply mirror the public headers in our existing > src/ hierarchy into /usr/include/openocd[-<version>]/, such that > applications can use -I<that_path> and #include <<module>/<header>.h>. > Indeed, I have a series of patches that accomplishes these changes for > all <module>s and <header>s in the tree. (Via a script, so it's easy to > recreate its patches when I get merge conflicts.)
As I mentioned in another thread, I am going to finish this series and push it shortly. Speak now if you object. --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
