On Tue, 17 Feb 2009, Szak�ts Viktor wrote: Hi Viktor,
> Yes, until further testing I didn't want touch the package creation files. > They still refer to hbmake, > which should be replaced with hbmk. > There is another problem, hbmk collides with > current hbmk script. The build process overwrites > the hbmk executable with the script of the same > name. > For the transition I'd like to ask group opinion on > renaming hbmk script to hbmko or hbmks. The > script should stay until hbmk works and has all > needed features (see the list in ChangeLog). > Also, I think it's time to remove some aliases > of hbmk: hbcc, hbcmp, hblnk, hb-build. > Przemek, what do think how to proceed? It will break all my projects and also 3-rd party ones which uses them. The naming convention is strict and I can use: hb* for harbour native compiler hbw* for harbour windows cross builds hbce* for harbour windows-ce cross builds xhb* for xhabrbour builds xhbw* for xhabrbour windows cross builds xharbour does not support win-ce so xhbce* scripts do not work. I need all of them and they can perfectly hide the installation differences and configuration. F.e. look at xHGtk project and Makefile.scr. One simple make file which can be used in all platforms to create different builds without setting any additional environment variables - only HB_PREF to chose the build type. Look also at make_gtk.sh: # --------------------------------------------------------------- # simple script to build XHGTK binaries using [x]hb*scripts # to hide platform differences # By default they looks for native Harbour then xHarbour scripts # It's possible to force build type using as 1-st parametr: # -hb # Harbour platform native binaries # -hbw # Harbour Win32 cross build binaries (MinGW32) # -hbce # Harbour WinCE cross build binaries (MinGW32-CE) # -xhb # xHarbour platform native binaries # -xhbw # Harbour Win32 cross build binaries (MinGW32) # -xhbce # Harbour WinCE cross build binaries (MinGW32-CE) It's really simple solution which safe me a lot of time working on different Harbour projects. As long as hbmk.prg will not support whole hb* scripts functionality then please leave the scripts with original names. To avoid name conflict we can rename hbmk.prg - it's not widely used tool yet so it should not be a problem now. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
