>
> IMO it is useful in this form:
> {bcc}workdir=...

A .hbp just plugs in into a build process and there can
be multiple .hbp files (even picked automatically), so
speccing workdir here is not the best, can create conflicts
or unexpected results for the user.


> >> 3.
>
>> -o<OutFileName> also cannot be defined in .hbp.
> >
> >
> > Also build/app/target specific option. .hbp is meant to accompany
> > 3rd party libs and in such file is best to leave out everything
> > which is app specific. What you need is probably an .hbm
> > file if you miss -o.
> >
>
> You already have implemented filters, no?
> So
> {bcc}outfile=c:\dev_exes\vouch.bcc
> {msvc}outfile=c:\dev_exes\vouch.msvc


Or even (in .hbm file or cmdline):
-oC:\dev_exes\vouch.${hb_comp}

I avoid one more parameter in routine batch file.
> What is the loss if it is implemented in .hbp also
> alongwith how it is behaving as of current.


It doesn't belong here. I think in your case it's
enough to use .hbm files and no .hbp files.


> > is present in regular script files and GNU make, and which makes them
> > much more complicated to use than necessary.
> >
>
> Ameen.
> What is the syntax of using ${ENVVAR} in .hbm files.
> It practically solves my purpose.


Well, just simply ${ENVVAR} :) where ENVVAR is the
name of your environment variable.

PS : I am asking so much because though xMate has served well
> all these years still I felt the punch of some very important missing
> features which Andy could never get a time to implement.


I didn't look closely into xMate project files yet, the goal wasn't to
mimic
it, anyhow since the purpose is similar you can probably find several
similarities in final implementation.

The basic idea of hbmk2 is that you can do everything in command
line and you can extend your command line into .hbm scripts which
use the exact same format as cmdline. Plus you can embed them.

.hbp files serve the specific purpose of accompanying libraries and
add that lib specific requirements to a given app build (project). So it's
not to be confused with "project files" used in some builders. Project
files are rather .hbms.

Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to