> > Works right also in library creation > hbmk2 delta.prg ACHOICE.PRG APPEND_D.PRG BOTTON_D.PRG CALCOL_ > D.PRG COLOR_D.PRG DEFOPT.PRG EDIDUP_D.PRG EDITA2_D.PRG EDITAR_D.PRG > ERROR_D.PRG > FILTRO_D.PRG GETSYS_D.PRG GRAFIC_D.PRG LABEL_D.PRG MENU.PRG OBSOL_D.PRG > OPEN_D. > PRG PATH_D.PRG PDRIV_D.PRG REPPAR_D.PRG SNAKE_D.PRG STACK_D.PRG > STRING_D.PRG TAB > RIG_D.PRG VALID_D.PRG VARIE_D.PRG VISTA2_D.PRG WORDPR_D.PRG -b -m > -D__GTWVT__ > -hblib -odelta4hhd.lib -info -trace -inc > hbmk: Using Harbour: c:\harbour\mingw\bin c:\harbour\mingw\include > c:\harbour\mi > ngw\lib c:\harbour\mingw\lib > hbmk: Processing configuration: c:\harbour\mingw\bin\hbmk.cfg > hbmk: Target up to date: libdelta4hhd.a > > I have same question > hbmk incremental process must/will know also if a lib was updated?
It will only know if someone implements this, it's in the TODO, but I see it quite problematic to solve in a generic way. I'll keep this in mind, maybe in the future I'll make some steps in this direction, but for now I'm happy with this stage. Your next question might be: "will it automatically rebuild if an included header is rebuilt?". Same thing applies, but I'm even less interested for now. Such mechanism is easy to tackle onto current logic, given someone writes such source parsing header following code. > if same library is created (for example) with and without debug can i > set diferent path for incremental? Yes, see -workdir: option. Since debug/release is a common thing, maybe we can extend default work dir with this information. We will see, first lets see if basics work. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
