Testing&comments appreciated!
I'm thinking that target executables should be placed
into the same folder as scripts.
It's not really executables from the host OS's point of
view, it's just data that ships w/OpenOCD and that
OpenOCD uses.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/helper/options.c
===================================================================
--- src/helper/options.c (revision 2490)
+++ src/helper/options.c (working copy)
@@ -105,6 +105,8 @@
/// @todo Implement @c add_script_search_dir("${HOME}/.openocd").
add_script_search_dir(PKGDATADIR "/site");
add_script_search_dir(PKGDATADIR "/scripts");
+ /// @todo where should target executables be placed?? For now in the
PKGDATADIR
+ add_script_search_dir(PKGDATADIR);
#endif
return ERROR_OK;
}
Index: src/target/Makefile.am
===================================================================
--- src/target/Makefile.am (revision 2490)
+++ src/target/Makefile.am (working copy)
@@ -95,8 +95,8 @@
mips32_dmaacc.h \
avrt.h
-nobase_dist_pkglib_DATA =
-nobase_dist_pkglib_DATA += xscale/debug_handler.bin
-nobase_dist_pkglib_DATA += ecos/at91eb40a.elf
+nobase_dist_pkgdata_DATA =
+nobase_dist_pkgdata_DATA += xscale/debug_handler.bin
+nobase_dist_pkgdata_DATA += ecos/at91eb40a.elf
MAINTAINERCLEANFILES = $(srcdir)/Makefile.in
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
