Hi All,

If we want to get the release out before 
xmas, I think we should now go to freeze 
officially and commit _fixes_ only, and 
most importantly _build fixes_.

Some preliminary notes/questions about the release:

- Embedded TDM dwarf-2 build doesn't work 
  with hbmk2 and I'm not sure it would be 
  good to include anyway a "double decker" 
  C compiler (with both gcc.exe and gcc-dw2.exe).
  (Plus it needs some heavier changes in hbmk2 code)
  Which means the official MinGW release 
  could only be used, but I doubt there will be 
  enough time to test it generally or test 
  it for embedded purposes. The installation is 
  extremely cumbersome and error prone as I wrote.
  Moreover I reported warning with QT 4.6 and MSVC, 
  and no one reacted, which means it's unlikely 
  to be fixed in a few days. MSVC + QT 4.6 is also 
  not fully tested or all linkage C RTL issues 
  fully cleared.
  This means the 2.0.0 windows binary release will support 
     QT 4.5.x.
  Anyone has any issue with this?
- whatsnew.txt is lacking, so unless someone 
  wants to deal with it in next few days, I'll add 
  a text saying:
  "and a lot more feature to be detailed later" 
  or alike.
- If the binary release is up to me, I'll 
  leave out DJGPP build, since I don't possess a 
  dev environment for it anymore. watcom/dos build 
  can be included, but I'm not sure if it's 
  worth it.
- Should we include watcom/os2 and watcom/linux
  in final win binary release? IMO the only 
  reason is for technological showcase, but 
  I doubt any win users would actually use these.
  Leaving it out saves build time, package size 
  and upload/download time.

Brgds,
Viktor

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

Reply via email to