Hi Przemek,
> 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 I don't see why these names need separate hbcc, hbcmp, hblnk and hb-build scripts. The 'hb' prefix would stay, in Harbour we don't have hbw, nor hbce, but we can create equivalents (even though I'd be personally happier with more generic solution). Anyhow I still don't see how this is related to these extra aliases. I have no intention to remove hb prefix. > Look also at make_gtk.sh: Swapping hbcmp to hbmk seems to solve the problem, if xhb has hbmk as well, if not it takes probably a few lines more to do the automatic detection. > 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. >From your words it looks hbmk.prg is the sole effort of mine without your support or too much chance to get grounds due to constraints posed by external project details, even though the new tool is meant to be a plugin replacement. And this makes it practically impossible to achieve any kind of simplification here. If this is the case I won't touch hbmk.prg anymore. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
