> 9) In the project properties would need a field to set the target
> platform and may be useful to make cross-build process.
>
> Target platform is just an hbmk2 switch: -plat=
>
> In HBIDE it was recently implemented as separate option with
> {hb_plat}, which uses HB_PLATFORM envvar. I don't know the
> reasons, this seems like overcomplicating this matter and
> HB_PLATFORM envvar is definitely a legacy solution, so using
> -plat= option directly seems to be the optimal solution here.
>
Please note that "Environments" protocol is designed for this
purpose only. I do not know how does hbMK2 works, I simply
accepting input from user and pushing forward to hbMK2.
May be this is not needed at all, and probably does not, tell me
what else I have to remove from hbide.env to make it crystal
clear. These are my grasp of the knowledge only which can be
limited.
-plat=option will be the final result of
{hb_pat} win == -plat=win
This is only a way to record this entry in "Environments".
Pritpal
--
View this message in context:
http://old.nabble.com/hbIDE---Requested-Thought-of-Features-Tracking-tp27313368p27314930.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
