Starting with FWH

[Otto]

As I alway have problems to compile the FWH-samples
I did today a clean installation - FORMAT c: - setup WINDOWS ...

But the same thing. After all only an error.

Regards
Otto

************************
1) download the all the files from the FTDN

2) copy all the files to a directory (FW_CD) and unpack setup.zip

start setup.exe

3) read Five Tech letter

4) Install Fivewin for Harbour/xHarbour
Fivewin for Harbour/xHarbour installation with default values

5) Install xHarbour (Borland build)
WARNING: xHarbour is not on the FTDN site - there you only load a link!!!

6) Install Borland C++ 5.5
There is a link on the fivewin-Homepage <FWH> to free Borland C++ 5.5

ftp://ftpd.borland.com/download/bcppbui ... etools.exe

7) your first FHW-programm

CMD
cd\
cd fwh
cd samples


buildx.bat fwbrow

+----------------------------------------------------------------------------+
¦ FiveWin for xHarbour 2.7 - June 2006 xHarbour development power ¦_
¦ (c) FiveTech, 1993-2006 for Microsoft Windows 95/98/NT/2000/ME and XP ¦¦
+----------------------------------------------------------------------------+¦
  ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Compiling...
xHarbour Compiler build 0.99.61 (SimpLex)
Copyright 1999-2006, http://www.xharbour.org http://www.harbour-project.org/
Compiling 'fwbrow.prg' and generating preprocessed output to 'fwbrow.ppo'...
Lines 407, Functions/Procedures 12
Generating C source output to 'fwbrow.c'...
Done.
Das System kann den angegebenen Pfad nicht finden.
Das System kann den angegebenen Pfad nicht finden.
* There are errors

C:\FWH\SAMPLES>

[Antonio Linares]

Otto,

> 7) your first FHW-programm

Before that step you have to edit buildx.bat and set your own paths.

> Das System kann den angegebenen Pfad nicht finden.

Could you translate it into English ? Thanks,

[Antonio Linares]

Otto,

>
5) Install xHarbour (Borland build)
WARNING: xHarbour is not on the FTDN site - there you only load a link!!!
>

Both Harbour and xharbour are free products, thats why we provide public urls to download them. You can get them from these forums at:
http://fivetechsoft.com/forums/viewtopic.php?t=2486

[Otto]

Hello Antonio,

>Before that step you have to edit buildx.bat and set your own paths.

Why do I have to change my own paths if I didn't change the defaults from your setup-CD.

I imagine that I am not a FW user since 1.4 that I am a beginner and that many of the younger boys/girls don't know bat-files and DOS anymore.

Which paths do I have to control? Or is there a tool I can use?

Regards
Otto

[Otto]

Now I changed the installation guide

6) Install Borland C++ 5.5
Select c:\bcc55 as target.

There are new errors:
Unable to open include file ...
Regards
Otto



************************
1) download the all the files from the FTDN

2) copy all the files to a directory (FW_CD) and unpack setup.zip

start setup.exe

3) read Five Tech letter

4) Install Fivewin for Harbour/xHarbour
Fivewin for Harbour/xHarbour installation with default values

5) Install xHarbour (Borland build)
WARNING: xHarbour is not on the FTDN site - there you only load a link!!!

6) Install Borland C++ 5.5
Select c:\bcc55 as target.

There is a link on the fivewin-Homepage <FWH> to free Borland C++ 5.5

ftp://ftpd.borland.com/download/bcppbui ... etools.exe

7) your first FHW-programm

CMD
cd\
cd fwh
cd samples


buildx.bat fwbrow


----------------------------------------------------------------------------+
¦ FiveWin for xHarbour 2.7 - June 2006 xHarbour development power ¦_
¦ (c) FiveTech, 1993-2006 for Microsoft Windows 95/98/NT/2000/ME and XP ¦¦
+----------------------------------------------------------------------------+¦
  ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Compiling...
xHarbour Compiler build 0.99.61 (SimpLex)
Copyright 1999-2006, http://www.xharbour.org http://www.harbour-project.org/
Compiling 'fwbrow.prg' and generating preprocessed output to 'fwbrow.ppo'...
Lines 407, Functions/Procedures 12
Generating C source output to 'fwbrow.c'...
Done.
Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
fwbrow.c:
Error E2209 c:\xharbour\include\hbdefs.h 56: Unable to open include file 'stdarg
.h'
Error E2209 c:\xharbour\include\hbdefs.h 57: Unable to open include file 'stdio.
h'
Error E2209 c:\xharbour\include\hbdefs.h 58: Unable to open include file 'stdlib
.h'
Error E2209 c:\xharbour\include\hbdefs.h 59: Unable to open include file 'string
.h'
Error E2209 c:\xharbour\include\hbsetup.h 61: Unable to open include file 'limit
s.h'
Error E2188 c:\xharbour\include\hbdefs.h 409: Expression syntax
Error E2257 c:\xharbour\include\hbdefs.h 434: , expected
Error E2139 c:\xharbour\include\hbvmpub.h 227: Declaration missing ;
Error E2451 fwbrow.c 90: Undefined symbol 'NULL'
Error E2141 fwbrow.c 90: Declaration syntax error
Error E2190 fwbrow.c 90: Unexpected }
Error E2190 fwbrow.c 90: Unexpected }
Error E2040 fwbrow.c 90: Declaration terminated incorrectly
Error E2190 fwbrow.c 196: Unexpected }
Error E2190 fwbrow.c 196: Unexpected }
Error E2109 fwbrow.c 196: Not an allowed type in function hb_vm_SymbolInit_FWBRO
W
*** 16 errors in Compile ***
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
Fatal: Unable to open file 'C0W32.OBJ'
* There are errors

C:\FWH\SAMPLES>

[Detlef Hoefner]

Hi Otto,

Nobody can know the setup of your BCC installation.

Please make sure that your PATH includes the folder 'bin' of BCC.
Example: d:\bcc55\bin;

In the standard makefile buildx.bat you must edit the following two lines :
set hdir=d:\xharbour
and
set bcdir=d:\bcc55

With this 3 modifacations i succeeded imediatelly building up my first FWH sample.

Keep cool

Best regards,
Detlef

[Antonio Linares]

Otto,

Besides Detlef explanation, as described at http://www.fivetechsoft.com/english/fwh.html you also have to create these files:

Borland installation is also an automatic process, though once it is completed, you must create the following ascii files: bcc32.cfg and ilink32.cfg and place them at c:\Your_selected_Borland_path\bin. Those files containts are as follows:

bcc32.cfg:

-I"c:\Your_selected_Borland_path\include"
-L"c:\Your_selected_Borland_path\lib"

ilink32.cfg:
-L"c:\Your_selected_Borland_path\lib"

Borland readme file also explains it very clearly.

[Otto]

Hello Antonio,
thank you for your help.
But at the moment I can't be bothered to go ahead with the fresh installation.
I have FWH working on my develop machine. Only sometimes buildx.bat doesn’t what I want.
Most times xBuildW.exe helps out.
I only thought to try out a fresh installation from a FW-marketing point of view. One click should do the job. But at the moment we are miles away from that. For a beginner it is really a hard job to start with FW !
Only now I saw that there are more explanations on your homepage.
(In fact of the disturbing background text is very hard to read. )
As I do not plan to use Advantage I didn’t read the Advantage section.
Conclusion ACE32.dll is missing.
Regards
Otto

[Detlef Hoefner]

Hi Otto,

you don't need every single line in buildx.bat.

You can put all advantage components into comment if you don't use Advantage RDD.

The same if you use only dbfntx rdd, you can put these two lines into comment.

echo %hdir%\lib\dbfcdx.lib + >> b32.bc
echo %hdir%\lib\dbffpt.lib + >> b32.bc

Just write a 'rem ' at the beginning of these lines and you'll feel young again

Best regards,
Detlef

[Antonio Linares]

Otto,

Please believe me if I tell you that you are the first one in years that complains about that

FW is very well known for its simplicity and its easy of use.

[Greg Gammon]

Just my 2 cents (don't know the Euro conversion sorry) worth....
It took me some time to figure out the correct installation setup for the buildH .bat file...and I know DOS. For those that have no DOS experience, this can be a daunting task. I found the documentation very vague. As more and more people get into programming that have no DOS experience, this could be an issue. I would suggest as part of the installation routine, you might want to create an install program that asks for all the paths and then creates the buildH.bat file from that. Simpler for the end user to get up and running quickly. Also should include in the docs that the buildH.bat file needs to be in the directory your program file resides in. Simple stuff, but not documented very well.

[Antonio Linares]

Greg,

> Just my 2 cents (don't know the Euro conversion sorry) worth....

We also have cents

We are going to review a default setup to see if we can make it more simpler...