After commenting line 50 in make_gnu_xmingwce.sh, and removing foreign tools from CCPATH, everything is back to normal. Using this script: --- set CCPATH=C:\devl\MinGW-410-ce\opt\mingw32ce\bin set PATH=C:\devl\msys\1.0.11\bin;%CCPATH%;%PATH% rem set HB_COMPILER=mingwce rem set HB_COMP_PATH=/c/devl/hbvc-1.1/bin/harbour.exe set HB_PPGEN_PATH=/c/devl/hbvc-1.1/bin/hbpp.exe rem set HB_INSTALL_PREFIX=/c/devl/hb%HB_COMPILER%-1.1-test sh make_gnu_xmingwce.sh -i install > out.txt 2>&1 exit ---
So I conclude line 50 probably needs tweaking for win, or it isn't necessary at all. After clearing this issue, I'd like to document mingwce cross build in INSTALL, plus also clean the cross-build section regarding HB_COMP_PATH and HB_PPGEN_PATH, which currently seems wrong, despite it's working. I think this matter needs some cleaning as currently make_gnu_x*.sh scripts are doing some magic on these variables, which makes their meaning different than when using the make system directly via make_gnu.bat. I think these should work the same way I'll also rename HB_PPGEN_PATH to HB_HBPP_PATH. Maybe after 1.1, but I was thinking to merge make_gnu_x*.sh into make_gnu.sh, to simplify things internally, to remove some redundancy and make build process more coherent for different situations. Probably make_gnu_x*.sh files can be reduced to 'HB_ARCHITECTURE=win, HB_COMPILER=mingw*, ./make_gnu.sg'. The rest can be done by detecting the host platform and doing necessary tricks accordingly. By now I have a mingwce build ready (which is great!), and the only flaw I've noticed that no binaries were generated, except hbpp.exe. Why could that be? Brgds, Viktor On Sat, Mar 14, 2009 at 11:17 AM, Viktor Szakáts <harbour...@syenar.hu>wrote: > set HB_PPGEN_PATH=/c/devl/hbvc-1.1/bin/hbpp.exe >> This also was in previous message. Sorry that it was not clear enough. > > > Thanks you, this bit was missing. > > Now, after doing a few changes, the results are the exact same. > If I use the Cygwin shell, it complains about missing 'harbour' > in PATH. If I use msys shell, it complains about missing 'make' > and 'cygwin1.dll'. All of the above is in the PATH. > > After experimenting a bit with procmon, I've found that the PATH isn't > properly searched, which lead me to line 50 of make_gnu_xmingwce.sh: > export PATH="$CCPATH:$PATH" > > Then I copied make.exe and cygwin1.dll into CCPATH, and if the > win/mingwce dirs are already present, the object file and libs are > being created both for .prg and .c files, which is a definite advance. > > Things get pretty unpredictable after this point, I was trying different > combinations of msys and non-msys make.exes with additional > external msys tools, but there are various errors both for clean and > install: > --- > '[' is not recognized as an internal or external command, > operable program or batch file. > The syntax of the command is incorrect. > --- > ! was unexpected at this time. > --- > ./bin/postinst.sh > process_begin: CreateProcess(NULL, sh > C:\work\harbour-new\harbour\bin\postinst.sh, ...) failed. > make (e=2): The system cannot find the file specified. > --- using msys make: > rm -f -r win/mingwce > make: rm: Command not found > 0 [main] make 1716 sync_with_child: child 4600(0x724) died before > initialization with status code 0x1 > 24409 [main] make 1716 sync_with_child: *** child state child loading > dlls > make: vfork: Resource temporarily unavailable > --- > > I speculate most of these are results of above PATH problem, > since normally my msys environment works flawlessly. > > Brgds, > Viktor > >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
