> I agree. > > Here is my argument: hbMK2 has filters parsing at -o level > which I cannot manage. I have requested you many times > to give a proper token to output name but you have always > deferred it. So what is wrong if I provide an option at -o > level or provide a slot as a field?
You have the final output name parsed from hbmk2 output so you don't need any of those, neither parsing -o option or maintain you own copy of it (which will most probably not emulate -o behavior properly). > I will retuen to this point a bit later to rework the detection logic. Why do you think it's me who should solve this problem for you? You pass me back this all the time, while you never have invested any effort to even understand or test this problem. > You stay in the folder where executable is, hbIDE do not. > Just provide a token with full path, that's it. No, you have to complete the non-absolute path to a relative one using current dir as a base, if your proprietary launching solution is unable to use current dir of caller application. Get back to me if these options failed. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
