On 04 Feb 2015, at 21:25, Peter Stuge <pe...@stuge.se> wrote: > Liviu Ionescu wrote: >> my experience with windows drivers is close to null, > > Then study.
thank you for this suggestion, I'll do it when really needed, but currently Windows has quite a low priority for me. >> my build procedures already compile libusb-1, libusb-0, > > What exactly does libusb-0 mean? libusb-compat-0.1.5 on Linux and OS X libusb-win32-1.2.6.0 on Windows > >> libusb-win32 and libftdi from sources > > libusb-win32 isn't really neccessary for you to build - it is only > neccessary for the kernel driver. it was required by openocd, when using the configure options I mentioned previously. (config.log) LIBUSB0_CFLAGS='-I/media/ilg/Work/openocd/install/win64/include/libusb ' LIBUSB0_LIBS='-L/media/ilg/Work/openocd/install/win64/lib -lusb ' > (and I have a custom pkg-config to detect them), > > Why? Why not do as the manual describes and use PKG_CONFIG_LIBDIR? "PKG_CONFIG_LIBDIR Replaces the default pkg-config search directory. PKG_CONFIG_PATH A colon-separated (on Windows, semicolon-separated) list of directories to search for .pc files. The default directory will always be searched after searching the path; the default is libdir/pkgconfig:datadir/pkgconfig where libdir is the libdir where pkg-config and datadir is the datadir where pkg-config was installed." my scripts use PKG_CONFIG_PATH to be sure I fully control the search path, to avoid finding anything in the system folders. >> thank you for helping clarify some of the issues. > > It is no simple matter to produce a correct and useful cross-compiled > version of any package. fully agree > It very much requires being familiar not only > with the package itself but also its dependencies and also how the > respective build systems work. right. except not knowing the best 'configure' options (and replicated the configuration used by Freddie Chopin, considered a 'classical'), I think the build scripts I used for all 3 platforms are quite elaborate. if you have any comments/suggestions/criticisms regarding these scripts, and the entire build procedures of the GNU ARM Eclipse OpenOCD, please address them, I have no problems with this as long as they are constructive. regards, Liviu ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
