FiveTech Software tech support forums

www.FiveTechSoft.com

Skip to content

FWH64

Post a reply

Re: FWH64

Postby Marc Vanzegbroeck » Mon Mar 21, 2016 7:21 pm

Antonio,

Do i have to make a GO64.BAT file, like you wrote in
http://forums.fivetechsupport.com/viewtopic.php?p=161675#p161675
but with other directories to create an exe in Visual Studio Community 2015?

Thanks
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Antonio Linares » Mon Mar 21, 2016 7:28 pm

Marc,

For a single PRG you can use FWH\samples\build64.bat

For several PRGs then you can use this makefile (you need to do some little changes)

viewtopic.php?p=162896#p162896
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42122
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Top

Re: FWH64

Postby Marc Vanzegbroeck » Mon Mar 21, 2016 8:11 pm

Antonio,

If I compile I get:
┌────────────────────────────────────────────────────────────────────────────┐
│ FWH 64 for Harbour 16.02 (MSVC++) Feb.2016       Harbour development power │▄
│ (c) FiveTech 1993-2016 for Microsoft Windows 9X/NT/200X/ME/XP/Vista/7/8/10 │█
└────────────────────────────────────────────────────────────────────────────┘█
  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Compiling...
Harbour 3.2.0dev (r1603082110)
Copyright (c) 1999-2016, http://harbour-project.org/
Compiling 'dlg.prg' and generating preprocessed output to 'dlg.ppo'...
Lines 4542, Functions/Procedures 1
Generating C source output to 'dlg.c'... Done.
cl wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
link wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
* Linking errors *

It seems that CL and LINK is not found.
I also can't find %ProgramFiles%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat or %ProgramFiles(x86)%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat that is in the buid64.bat file
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Antonio Linares » Mon Mar 21, 2016 8:51 pm

Marc,

You have to install Visual Studio Community 2015:

https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42122
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Top

Re: FWH64

Postby Marc Vanzegbroeck » Mon Mar 21, 2016 8:59 pm

Antonio Linares wrote:Marc,

You have to install Visual Studio Community 2015:

https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx


Antonio,

I already installed Visual Studio Community 2015...
The installpath is ""C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe"

Visual Studio Community 2015 is running fine, only linking FWH give some problems...
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Antonio Linares » Mon Mar 21, 2016 9:05 pm

Marc,

Then these lines from build64.bat should work fine:

if exist "%ProgramFiles%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" call "%ProgramFiles%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86_amd64
if exist "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" call "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86_amd64
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42122
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Top

Re: FWH64

Postby Marc Vanzegbroeck » Mon Mar 21, 2016 10:26 pm

Antonio,

I already change those lines, with no result
In these directories are no files, only subdirectories.
Image

What should be in that bat-file?
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby TimStone » Mon Mar 21, 2016 11:45 pm

Marc,

I just checked my install, and it is in the VC folder, not in one of the subfolders. When you installed Community, did you elect for the complete package ? That might help.

Tim
Tim Stone
http://www.MasterLinkSoftware.com
http://www.autoshopwriter.com
timstone@masterlinksoftware.com
Using: FWH 23.10 with Harbour 3.2.0 / Microsoft Visual Studio Community 2022-24 32/64 bit
User avatar
TimStone
 
Posts: 2945
Joined: Fri Oct 07, 2005 1:45 pm
Location: Trabuco Canyon, CA USA
Top

Re: FWH64

Postby Marc Vanzegbroeck » Tue Mar 22, 2016 6:26 am

Tim,

After selecting all, the file exist :D
Thank you.
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Marc Vanzegbroeck » Tue Mar 22, 2016 7:43 am

Antonio, is it possible that not all files are included in the package?
Now I got this error.

┌────────────────────────────────────────────────────────────────────────────┐
│ FWH 64 for Harbour 16.02 (MSVC++) Feb.2016 Harbour development power │▄
│ (c) FiveTech 1993-2016 for Microsoft Windows 9X/NT/200X/ME/XP/Vista/7/8/10 │█
└────────────────────────────────────────────────────────────────────────────┘█
  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Compiling...
Harbour 3.2.0dev (r1603082110)
Copyright (c) 1999-2016, http://harbour-project.org/
Compiling 'xbrwin7.prg' and generating preprocessed output to 'xbrwin7.ppo'...
Lines 4828, Functions/Procedures 1
Generating C source output to 'xbrwin7.c'... Done.
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23506 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

xbrwin7.c
c:\_vmsdata\fwh64\harbour64\include\hbdefs.h(51): fatal error C1083: Cannot open
include file: 'stdio.h': No such file or directory
LINK : fatal error LNK1181: cannot open input file 'xbrwin7.obj'
* Linking errors *
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Marc Vanzegbroeck » Tue Mar 22, 2016 9:16 am

Hi,

Now I got this error:
┌────────────────────────────────────────────────────────────────────────────┐
│ FWH 64 for Harbour 16.02 (MSVC++) Feb.2016 Harbour development power │▄
│ (c) FiveTech 1993-2016 for Microsoft Windows 9X/NT/200X/ME/XP/Vista/7/8/10 │█
└────────────────────────────────────────────────────────────────────────────┘█
  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Compiling...
Harbour 3.2.0dev (r1603082110)
Copyright (c) 1999-2016, http://harbour-project.org/
Compiling 'xbrwin7.prg' and generating preprocessed output to 'xbrwin7.ppo'...
Lines 4828, Functions/Procedures 1
Generating C source output to 'xbrwin7.c'... Done.
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23506 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

xbrwin7.c
LINK : fatal error LNK1181: cannot open input file 'c:\_vmsdata\FWH64\harbour64\
lib\vc64\hbrtl.lib'
* Linking errors *

In the build64.bat file is the path hdirl set to set hdirl=%hdir%\lib\vc64
but there is no subdirectory VC64
I changed the path to set hdirl=%hdir%\lib and now it's working. :D :D :D :D :D

Are are the LIB's in lib-directory maybe for VC64?
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Antonio Linares » Tue Mar 22, 2016 10:36 am

Marc,

If you create a c:\harbour\lib\vc64 folder and copy there the Harbour 64 libs then it will work fine
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42122
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Top

Re: FWH64

Postby Marc Vanzegbroeck » Tue Mar 22, 2016 2:28 pm

Antonio,

I want to create a MAK-file for my projects mith more than one PRG-file, but I get an error.

I want to create the example 'toolbar2.prg'.
Creating it with build64.bat works fine.

The MAK-file give the error :
Code: Select all  Expand view  RUN
c:\_vmsdata\FWH64\projects\EPKSDoc\prg>if exist "C:\Program Files (x86)\Microsof
t Visual Studio 14.0\VC\vcvarsall.bat" call "C:\Program Files (x86)\Microsoft Vi
sual Studio 14.0\VC\vcvarsall.bat"

Microsoft (R) Program Maintenance Utility Version 14.00.23506.0
Copyright (C) Microsoft Corporation.  All rights reserved.

NMAKE : fatal error U1071: cycle in dependency tree for target 'TOOLBAR2.PRG'
Stop.


This is my go.bat file
Code: Select all  Expand view  RUN
@set oldpath=%path%
@set oldinclude=%include%
@set oldlib=%lib%
@set oldlibpath=%libpath%
if exist "%ProgramFiles%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" call "%ProgramFiles%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat"
if exist "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" call "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\VC\vcvarsall.bat"
c:\"Program Files (x86)\Microsoft Visual Studio 14.0"\VC\bin\nmake -fTOOLBAR2.mak
@set path=%oldpath%
@set include=%oldinclude%
@set lib=%oldlib%
@set libpath=%oldlibpath%
@set oldpath=""
@set oldinclude=""
@set oldlib=
@set oldlibpath=
if errorlevel==0 TOOLBAR2.exe


and this is the MAK-file
Code: Select all  Expand view  RUN
#Microsoft Visual-Studio Community 2015, (c) FiveTech Software 2016

HBDIR=C:\_vmsdata\FWH64\harbour64
FWDIR=C:\_vmsdata\FWH64\fwh64
VCDIR="c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC"
SDKDIR="c:\Program Files (x86)\Windows Kits\8.1"

PRGS =       \
   TOOLBAR2.PRG  \

.SUFFIXES: .prg .c .obj .rc .res

TOOLBAR2.exe : $(PRGS:.prg=.obj) TOOLBAR2.res
   echo $(PRGS:.prg=.obj) > msvc.tmp

   echo $(FWDIR)\lib\FiveH64.lib $(FWDIR)\lib\FiveHC64.lib >> msvc.tmp

   echo $(HBDIR)\lib\hbrtl.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbvm.lib     >> msvc.tmp
   echo $(HBDIR)\lib\gtgui.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hblang.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbmacro.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbrdd.lib    >> msvc.tmp
   echo $(HBDIR)\lib\rddntx.lib   >> msvc.tmp
   echo $(HBDIR)\lib\rddcdx.lib   >> msvc.tmp
   echo $(HBDIR)\lib\rddfpt.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbsix.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbdebug.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbcommon.lib >> msvc.tmp
   echo $(HBDIR)\lib\hbpp.lib     >> msvc.tmp
   echo $(HBDIR)\lib\hbcpage.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbwin.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbct.lib     >> msvc.tmp
   echo $(HBDIR)\lib\hbziparc.lib >> msvc.tmp
   echo $(HBDIR)\lib\hbmzip.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbzlib.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbpcre.lib   >> msvc.tmp
   echo $(HBDIR)\lib\minizip.lib  >> msvc.tmp
   echo $(HBDIR)\lib\xhb.lib      >> msvc.tmp
   echo $(HBDIR)\lib\hbcplr.lib   >> msvc.tmp
   echo $(HBDIR)\lib\png.lib      >> msvc.tmp

   echo kernel32.lib  >> msvc.tmp
   echo user32.lib    >> msvc.tmp
   echo gdi32.lib     >> msvc.tmp
   echo winspool.lib  >> msvc.tmp
   echo comctl32.lib  >> msvc.tmp
   echo comdlg32.lib  >> msvc.tmp
   echo advapi32.lib  >> msvc.tmp
   echo shell32.lib   >> msvc.tmp
   echo ole32.lib     >> msvc.tmp
   echo oleaut32.lib  >> msvc.tmp
   echo uuid.lib      >> msvc.tmp
   echo odbc32.lib    >> msvc.tmp
   echo odbccp32.lib  >> msvc.tmp
   echo iphlpapi.lib  >> msvc.tmp
   echo mpr.lib       >> msvc.tmp
   echo version.lib   >> msvc.tmp
   echo wsock32.lib   >> msvc.tmp
   echo msimg32.lib   >> msvc.tmp
   echo oledlg.lib    >> msvc.tmp
   echo psapi.lib     >> msvc.tmp
   echo gdiplus.lib   >> msvc.tmp
   echo winmm.lib     >> msvc.tmp
   echo vfw32.lib     >> msvc.tmp

   IF EXIST TOOLBAR2.res echo TOOLBAR2.res >> msvc.tmp

   link @msvc.tmp /nologo /subsystem:windows /NODEFAULTLIB:msvcrt > link.log
   @type link.log
   @del $(PRGS:.prg=.obj)

$(PRGS:.prg=.obj) : $(PRGS:.prg=.c)
$(PRGS:.prg=.c) : $(PRGS)

TOOLBAR2.res : TOOLBAR2.rc
   rc.exe -r -d__FLAT__ TOOLBAR2.rc

.prg.c:
   $(HBDIR)\bin\harbour $< /n /i$(FWDIR)\include;$(HBDIR)\include

.c.obj:
   cl.exe -c -TC -W3 -I$(HBDIR)\include -I$(SDKDIR)\include -I$(VCDIR)\include $<
 
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top

Re: FWH64

Postby Antonio Linares » Tue Mar 22, 2016 3:58 pm

Marc,

If you use uppercase here:

PRGS = \
TOOLBAR2.PRG

Then you have to use upper case here too:

TOOLBAR2.exe : $(PRGS:.PRG=.OBJ) TOOLBAR2.res

and here:

$(PRGS:.PRG=.OBJ) : $(PRGS:.PRG=.C)
$(PRGS:.PRG=.C) : $(PRGS)
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42122
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Top

Re: FWH64

Postby Marc Vanzegbroeck » Tue Mar 22, 2016 7:08 pm

Antonio,

I have slill a problem.

I have changed the MAK-file to
Code: Select all  Expand view  RUN
#Microsoft Visual-Studio Community 2015, (c) FiveTech Software 2016

HBDIR=C:\_vmsdata\FWH64\harbour64
FWDIR=C:\_vmsdata\FWH64\fwh64
VCDIR="c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC"
SDKDIR="c:\Program Files (x86)\Windows Kits\8.1"

PRGS =       \
   toolbar2.prg

.SUFFIXES: .prg .c .obj .rc .res

toolbar2.exe : $(PRGS:.prg=.obj) toolbar2.res
   echo $(PRGS:.prg=.obj) > msvc.tmp

   echo $(FWDIR)\lib\FiveH64.lib $(FWDIR)\lib\FiveHC64.lib >> msvc.tmp

   echo $(HBDIR)\lib\hbrtl.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbvm.lib     >> msvc.tmp
   echo $(HBDIR)\lib\gtgui.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hblang.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbmacro.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbrdd.lib    >> msvc.tmp
   echo $(HBDIR)\lib\rddntx.lib   >> msvc.tmp
   echo $(HBDIR)\lib\rddcdx.lib   >> msvc.tmp
   echo $(HBDIR)\lib\rddfpt.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbsix.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbdebug.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbcommon.lib >> msvc.tmp
   echo $(HBDIR)\lib\hbpp.lib     >> msvc.tmp
   echo $(HBDIR)\lib\hbcpage.lib  >> msvc.tmp
   echo $(HBDIR)\lib\hbwin.lib    >> msvc.tmp
   echo $(HBDIR)\lib\hbct.lib     >> msvc.tmp
   echo $(HBDIR)\lib\hbziparc.lib >> msvc.tmp
   echo $(HBDIR)\lib\hbmzip.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbzlib.lib   >> msvc.tmp
   echo $(HBDIR)\lib\hbpcre.lib   >> msvc.tmp
   echo $(HBDIR)\lib\minizip.lib  >> msvc.tmp
   echo $(HBDIR)\lib\xhb.lib      >> msvc.tmp
   echo $(HBDIR)\lib\hbcplr.lib   >> msvc.tmp
   echo $(HBDIR)\lib\png.lib      >> msvc.tmp

   echo kernel32.lib  >> msvc.tmp
   echo user32.lib    >> msvc.tmp
   echo gdi32.lib     >> msvc.tmp
   echo winspool.lib  >> msvc.tmp
   echo comctl32.lib  >> msvc.tmp
   echo comdlg32.lib  >> msvc.tmp
   echo advapi32.lib  >> msvc.tmp
   echo shell32.lib   >> msvc.tmp
   echo ole32.lib     >> msvc.tmp
   echo oleaut32.lib  >> msvc.tmp
   echo uuid.lib      >> msvc.tmp
   echo odbc32.lib    >> msvc.tmp
   echo odbccp32.lib  >> msvc.tmp
   echo iphlpapi.lib  >> msvc.tmp
   echo mpr.lib       >> msvc.tmp
   echo version.lib   >> msvc.tmp
   echo wsock32.lib   >> msvc.tmp
   echo msimg32.lib   >> msvc.tmp
   echo oledlg.lib    >> msvc.tmp
   echo psapi.lib     >> msvc.tmp
   echo gdiplus.lib   >> msvc.tmp
   echo winmm.lib     >> msvc.tmp
   echo vfw32.lib     >> msvc.tmp

   IF EXIST toolbar2.res echo toolbar2.res >> msvc.tmp

   link @msvc.tmp /nologo /subsystem:windows /force:multiple > link.log
   @type link.log
   @del $(PRGS:.prg=.obj)

$(PRGS:.prg=.obj) : $(PRGS:.prg=.c)
$(PRGS:.prg=.c) : $(PRGS)

toolbar2.res : toolbar2.rc
   rc.exe -r -d__FLAT__ toolbar2.rc

.prg.c:
   $(HBDIR)\bin\harbour $< /n /i$(FWDIR)\include;$(HBDIR)\include /w /p /d__64__ %2 %3

.c.obj:
   cl.exe -c -TC -W3 -I$(HBDIR)\include -I$(SDKDIR)\include -I$(VCDIR)\include $<
 


And got
Code: Select all  Expand view  RUN
       echo psapi.lib     >> msvc.tmp
        echo gdiplus.lib   >> msvc.tmp
        echo winmm.lib     >> msvc.tmp
        echo vfw32.lib     >> msvc.tmp
        IF EXIST toolbar2.res echo toolbar2.res >> msvc.tmp
        link @msvc.tmp /nologo /subsystem:windows /force:multiple > link.log
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.


This is the link.log-file
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TWINDOW
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TIMAGELIST
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TBITMAP
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_GETWNDDEFAULT
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_NRGB
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TREBAR
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TTOOLBAR
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_MSGINFO
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_TSTATUSBAR
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_MENUBEGIN
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_MENUADDITEM
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_MENUEND
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_FW_GT
    toolbar2.obj : error LNK2001: unresolved external symbol _HB_FUN_ERRORSYS
    toolbar2.obj : error LNK2019: unresolved external symbol _hb_vmExecute referenced in function _HB_FUN_MAIN
    toolbar2.obj : error LNK2019: unresolved external symbol _hb_vmProcessSymbols referenced in function _hb_vm_SymbolInit_TOOLBAR2
    LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved external symbol _WinMain@16 referenced in function "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ)
    C:\_vmsdata\FWH64\fwh64\lib\FiveH64.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\fwh64\lib\FiveHC64.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbrtl.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbvm.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\gtgui.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hblang.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbmacro.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbrdd.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\rddntx.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\rddcdx.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\rddfpt.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbsix.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbdebug.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbcommon.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbpp.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbcpage.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbwin.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbct.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbziparc.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbmzip.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbzlib.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbpcre.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\minizip.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\xhb.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\hbcplr.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    C:\_vmsdata\FWH64\harbour64\lib\png.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
    toolbar2.exe : fatal error LNK1120: 17 unresolved externals
Regards,
Marc

FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc Vanzegbroeck
 
Posts: 1159
Joined: Mon Oct 17, 2005 5:41 am
Location: Belgium
Top
PreviousNext
Post a reply

Return to FiveWin for Harbour/xHarbour

Who is online

Users browsing this forum: No registered users and 33 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group