Nageswararao,
We publish xHarbour the same day that we download it from the CVS, once we run all our tests here.
So our build date is the CVS date
Error with xHArbour of FW8.02
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
This is the output generated in response to the command harbour /build
When the build includes changes upto 10th feb 2008, why does the output say the build has last change long dated 2007-10-31 and last CVS v. 1.5756 ?
Is it a bug in xHarbour or is there a way to build xharbour to reflect the correct info?
Code: Select all
xHarbour Compiler build 1.1.0 (SimpLex)
Copyright 1999-2008, http://www.xharbour.org http://www.harbour-project.org/
Harbour Build Info
---------------------------
Version: xHarbour build 1.1.0 Intl. (SimpLex)
PCode Version: 9
Compiler: Borland C++ 5.5.1 (32 bit)
Platform: Windows XP Professional 5.01.2600 Service Pack 2
Built on: Feb 10 2008 20:41:04
Last ChangeLog entry: 2007-10-31 17:12 UTC+0100 Miguel Angel Marchuet <miguelangel/at/marchuet.net>
ChangeLog CVS version: ChangeLog,v 1.5756
Harbour extensions: Yes
CA-Clipper 5.2e undocumented: Yes
CA-Clipper 5.2e strict compatibility: No
CA-Clipper 5.3x compatible extensions: Yes
Alaska Xbase++ compatible extensions: Yes
CA-Visual Objects compatible extensions: No
Multisoft Flagship compatible extensions: Yes
Microsoft FoxPro compatible extensions: No
dBase compatible extensions: No
Object file generation support: No
ANSI C usage: Non strict
C++ mode: Off
Compiler YACC debug mode: Off
Memory tracing and statistics: Off
Maximum symbol name length: 63
---------------------------
Is it a bug in xHarbour or is there a way to build xharbour to reflect the correct info?
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India