> I do not know if it will make-up in hnMK2,
> I understand your concerns, but the code below, 
> and I am sure it has greater margins to be refined,
> if included in hbMK2 will solve the problem for 
> applications which mix compile time switches 
> in not an organized way. It also does not break 
> anything in hbMK2, simply hangs in untils 
> someone uses it :
> 
> Line # 3996 ( a couple of lines up )
> ======================================
> 
>         /* Use external compiler */
> 
> ================================================
> 
> I know it is not the right way, but not to investigate in hbMK2,
> I could get this large projects compiled and linked with hbIDE.

Sorry to say, but I'd simply never do anything 
like that and such thing as "hello.prg;-w2". I'm 
not even sure why anyone would want to use hbmk2 
at all when dealing with such a mess. It's 
probably much easier to create a simple batch 
file and hack that to death.

It's not that I could not program some solution 
for it (given some days of efforts), but rather 
that I find this idea bleeding in several ways, 
and I like the notion to present solution so that 
they somehow push towards a better, simpler workflow 
(as opposed to adapt to _any_ workflow, included 
flawed ones).

It's like asking for a Mercedes and then 
attaching a fifth wheel to it and painting 
in gradient yellow with blue spots.

We have lots of other build tools to cover any 
existing build situation, f.e. GNU Make, or 
Borland make, nmake, etc.

I believe you have better options. F.e. you could 
fix the pragma mess, or wait our own fix for the 
pragmas. You could also hand sort the list of 
.prg files so that they don't cause problems, 
or use .clp files, or build the .prgs with 
common options into separate static libs and 
link them to the final executable. For these 
latter ones you wouldn't even have to touch the 
source. Of course the ultimate solution would 
be to see why the same project needs different 
compilation options, and fix it.

Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to