Page 1 of 1
Problems with 2.7 and xhb , februar build
Posted: Thu Jan 26, 2006 8:48 am
by Frank Demont
Hello
I can build and run a big aplication ( Thanks antonio , text.obj seems to work) , but have problems with samples from FW
So , i tryed alaska.prg , with his asociated rc-file
When xrc is called , i receive ton's off errors and warnings , to much to include ( 66.000 bytes)
Am i missing something ?
Frank
Posted: Thu Jan 26, 2006 9:15 am
by Antonio Linares
Frank,
samples\Alaska.prg properly builds with Borland and Microsoft too. So I guess it is something specific to xharbour xrc.
Could you please post the first 10 errors or so ? Thanks
Posted: Thu Jan 26, 2006 9:28 am
by Frank Demont
Type: C >>>xrc.exe -fo"objx\alaska.res" -I"D:\XhbFeb\c_include" -I"D:\XhbFeb\c_include\win" "alaska.rc"<<<
xRC: D:\XhbFeb\include\wintypes.ch(19): warning: Unknown preprocessor control: 'Ifndef'.
xRC: D:\XhbFeb\include\wintypes.ch(76): error: #endif with no #if.
xRC: D:\XhbFeb\include\cstruct.ch(87): warning: Unknown preprocessor control: 'xcommand'.
xRC: D:\XhbFeb\include\cstruct.ch(90): warning: Unknown preprocessor control: 'xtranslate'.
xRC: D:\XhbFeb\include\cstruct.ch(91): warning: Unknown preprocessor control: 'xtranslate'.
xRC: D:\XhbFeb\include\cstruct.ch(94): warning: Unknown preprocessor control: 'xcommand'.
xRC: D:\XhbFeb\include\cstruct.ch(103): warning: Unknown preprocessor control: 'xcommand'.
xRC: D:\XhbFeb\include\cstruct.ch(106): warning: Unknown preprocessor control: 'xcommand'.
xRC: D:\XhbFeb\include\cstruct.ch(108): warning: Unknown preprocessor control: 'xcommand'.
.......
xRC: D:\XhbFeb\include\wintypes.ch(76): error: File not found: '#endif'.
xRC: D:\XhbFeb\include\winuser.ch(1): error: File not found: 'from'.
xRC: D:\XhbFeb\include\winuser.ch(1): error: File not found: 'hConvert.EXE'.
........
Frank
Posted: Thu Jan 26, 2006 10:42 am
by Antonio Linares
Frank,
Please remove this line in alaska.rc:
#include "..\include\winapi.ch"
and add this one (at the beginning):
#include <windows.h>
Posted: Thu Jan 26, 2006 12:06 pm
by Frank Demont
Antonio
I don't understand. In this version from xhb are in the include file winapi.ch , wintypes.ch and winuser.ch present , not in the previous version. So i suppose that winapi.ch from this directory was used , not from fwh
I have also put this thread on xharbour , but no response
Type: C >>>xrc.exe -fo"objx\alaska.res" -I"D:\xHBFeb\c_include" -I"D:\xHBFeb\c_include\win" "alaska.rc"<<<
xRC: D:\xHBFeb\c_include\win\winuser.h(1008): warning: Macro redefinition of 'WS_OVERLAPPEDWINDOW'.
xRC: D:\xHBFeb\c_include\win\winuser.h(1009): warning: Macro redefinition of 'WS_POPUPWINDOW'.
xRC: D:\xHBFeb\c_include\win\winuser.h(1010): warning: Macro redefinition of 'WS_CHILDWINDOW'.
xRC: D:\xHBFeb\c_include\win\winuser.h(1032): warning: Macro redefinition of 'WS_EX_OVERLAPPEDWINDOW'.
xRC: D:\xHBFeb\c_include\win\winuser.h(1033): warning: Macro redefinition of 'WS_EX_PALETTEWINDOW'.
xRC: D:\xHBFeb\c_include\win\winuser.h(2250): warning: Macro redefinition of 'DS_SHELLFONT'.
xRC: D:\xHBFeb\c_include\win\winuser.h(2346): warning: Macro redefinition of 'LBS_STANDARD'.
xRC: D:\xHBFeb\c_include\win\commctrl.h(269): warning: Macro redefinition of 'CCS_LEFT'.
xRC: D:\xHBFeb\c_include\win\commctrl.h(270): warning: Macro redefinition of 'CCS_RIGHT'.
xRC: D:\xHBFeb\c_include\win\commctrl.h(271): warning: Macro redefinition of 'CCS_NOMOVEX'.
xRC: D:\xHBFeb\c_include\win\commctrl.h(791): warning: Macro redefinition of 'TBSTYLE_CHECKGROUP'.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
xRC: alaska.rc(17): error: Invalid syntax.
Type: C >>>Couldn't build: alaska.res<<<
Type: C >>>TMAKEOBJECT<<<
Type: C >>>TMAKEOBJECT:REFRESH<<<
Type: N >>> 1263<<<
Posted: Thu Jan 26, 2006 1:56 pm
by Antonio Linares
Frank,
If xHB is providing a winapi.ch too then there may be conflicts with FWH one, yes.