Well, I had to resort to the old method and unpack the .tgz under OS X (or Linux), and copy back the results.
It's possible to do on Windows also, if the gzipping is done with gzip and the untar using a working tar.exe. MinGW 4.3.2 has one. [ For me it's still a miracle how in 2009 there isn't a fully operational tar.exe for Windows. And also why someone distributes stuff in .tgz (with links!) for Windows... ] Brgds, Viktor On Fri, Mar 13, 2009 at 10:44 PM, Viktor Szakáts <harbour...@syenar.hu>wrote: > Hi Przemek, > > >> Not of the above is correct. >> In C:\devl\a\opt\mingw32ce\arm-wince-mingw32ce\bin you have ARM WinCE >> binaries. > > > No, I can run them in XP. > > >> In C:\devl\a\opt\mingw32ce\libexec\gcc\arm-wince-mingw32ce\4.1.0\ >> are GCC binaries which does not have to be in PATH. They are internally >> accessed by x86 binaries. > > > Yes, only three executables are there (cc1.exe notably), and > if they aren't in PATH, gcc.exe complains that it cannot execute > cc1.exe, that's why I added it. > > >> x86 binaries are in C:\devl\a\opt\mingw32ce\bin directory. >> and only this directory you should have in the PATH. > > > Yes, that's what I wanted to do first, however, it's impossible > that would work, since I have these files in that directory (note > the file lengths): > > arm-wince-mingw32ce-gccbug | 16,115 > arm-wince-mingw32ce-gcc-4.1.0 | 360,474 > arm-wince-mingw32ce-addr2line.exe | 1,253,266 > arm-wince-mingw32ce-ar.exe | 0 > arm-wince-mingw32ce-as.exe | 0 > arm-wince-mingw32ce-c++.exe | 364,076 > arm-wince-mingw32ce-c++filt.exe | 1,244,394 > arm-wince-mingw32ce-cpp.exe | 362,556 > arm-wince-mingw32ce-dlltool.exe | 0 > arm-wince-mingw32ce-g++.exe | 0 > arm-wince-mingw32ce-gcc.exe | 0 > arm-wince-mingw32ce-gcov.exe | 133,835 > arm-wince-mingw32ce-gdb.exe | 2,740,579 > arm-wince-mingw32ce-gprof.exe | 1,387,383 > arm-wince-mingw32ce-ld.exe | 0 > arm-wince-mingw32ce-nm.exe | 0 > arm-wince-mingw32ce-objcopy.exe | 1,743,015 > arm-wince-mingw32ce-objdump.exe | 0 > arm-wince-mingw32ce-ranlib.exe | 0 > arm-wince-mingw32ce-readelf.exe | 695,907 > arm-wince-mingw32ce-run.exe | 645,229 > arm-wince-mingw32ce-size.exe | 1,119,616 > arm-wince-mingw32ce-strings.exe | 1,118,936 > arm-wince-mingw32ce-strip.exe | 0 > arm-wince-mingw32ce-stub.exe | 13,312 > arm-wince-mingw32ce-windres.exe | 1,454,368 > > My untgz32.exe tool GPF-ed when uncompressing the .tar.gz > file, so I've used 7z.exe to unpack it. > > > set HB_BIN_COMPILE=/c/devl/hbvc-1.1/bin >> >> This is internal variables fortunately overwritten. Otherwise you'd lost >> /c/devl/hbvc-1.1/bin directory. >> I guess you want to set HB_COMP_PATH. It's necessary only if you do not >> want to use native binaries from Harbour source tree created by gcc (MinGW >> in Windows). In such case you should set full path with file name to >> harbour >> compiler, f.e.; >> set HB_COMP_PATH=/c/devl/hbvc-1.1/bin/harbour.exe >> >> > set HB_PPGEN_PATH=%HB_BIN_COMPILE% >> >> as above. Necessery only if you do not want to use native binaries from >> Harbour source tree. Shuld have full path with hbpp file name. > > > I'm afraid I don't get it, sorry. I've been using these sine 1.0.0 > release (successfully), and even documented them in INSTALL, and > here on the list as the proper ways to setup location of native binaries. > > What is the proper way then? How to point to hbpp.exe? > > Brgds, > Viktor > >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
