It seems this never reached the list... So in conclusion, the (soon to be official?) windows packages from Freddie Chopin installs config files so they are found by the first default search path (in $installroot). In a unix-like environment, including cygwin/msys, the build system by default installs them in $installroot/share/openocd/scripts, not yet covered by any default search path when building for Windows. I take the silence to mean that nobody wants the files under $installroot/lib/openocd so that search path could go (or possibly kept as a third option).
Any objections to merge this? Regards, Andreas 2010/1/16 Andreas Fritiofson <[email protected]>: > 2010/1/15 <[email protected]>: >> Użytkownik <[email protected]> napisał: >>>I find it odd that none has. >> >> Personally I don't know what is the point of that patch. I don't use OpenOCD >> via tree of MinGW/MSYS and I don't think anyone does, so what's the point of >> that patch? I use MinGW/MSYS to compile OpenOCD, and it compiles fine, >> because that process does not require cfg files. In windows there is only >> one place for installing software - C:\Program Files\. Personally I package >> OpenOCD the same way as Michael Fisher has done that in the past: /bin/ (exe >> + dll), /interface/ (cfg), /target/ (cfg), /board/ (cfg) and that works as a >> charm. > > Well, I do. Otherwise I wouldn't need it patched. So does everybody > else that uses a MSYS environment and wants to build/install openocd > with a customary configure && make && make install. This is the > environment we use at work, hence my wish to get it fixed. For my > personal use I don't really care since I don't use Windows. > > The reason I want packagers to comment is to avoid breakage if they > install scripts in ../lib relative to the openocd binary. > > Regards, > Andreas > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
