FWH64
-
- Posts: 1102
- Joined: Mon Oct 17, 2005 5:41 am
- Location: Belgium
- Contact:
Re: FWH64
Finally it's running!!!
Now I can really starting testing the 64lib
Now I can really starting testing the 64lib
Regards,
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
-
- Posts: 1102
- Joined: Mon Oct 17, 2005 5:41 am
- Location: Belgium
- Contact:
Re: FWH64
Antonio,
When I want to create testodbc.prg with build64.bat, I get this error:
Do I have to link something extra?
When I want to create testodbc.prg with build64.bat, I get this error:
Code: Select all
Compiling...
Harbour 3.2.0dev (r1603082110)
Copyright (c) 1999-2016, http://harbour-project.org/
Compiling 'testodbc.prg' and generating preprocessed output to 'testodbc.ppo'...
Lines 4861, Functions/Procedures 5
Generating C source output to 'testodbc.c'... Done.
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23506 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
testodbc.c
Microsoft (R) Windows (R) Resource Compiler Version 6.3.9600.17336
Copyright (C) Microsoft Corporation. All rights reserved.
testodbc.RC(13) : warning RC4005: 'ES_PASSWORD' : redefinition
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLTRANSACT
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETIN32
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLPREP32
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLSETCURSORNAME
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETCURSORNAME
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLTABLES
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLSTATISTICS
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLCOLUMNS
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLDRVC32
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLDESC32
FiveH64.lib(ODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETD32
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFREESTMT
FiveH64.lib(TDBODBCD.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFREESTMT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFETCH
FiveH64.lib(TDBODBCD.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFETCH
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLALLOCENV
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLALLOCCONNECT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLSETCONNECTOPTION
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLDISCONNECT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFREECONNECT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLFREEENV
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLALLOCSTMT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLNUMRESULTCOLS
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLEXECDIRECT
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETCONNECTOPTION
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLROLLBACK
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETDIAGREC
FiveH64.lib(TDBODBCD.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLGETDIAGREC
FiveH64.lib(TODBC.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLERROR
FiveH64.lib(TDBODBCD.obj) : error LNK2001: unresolved external symbol HB_FUN_SQLPRIMARYKEYS
testodbc.exe : fatal error LNK1120: 27 unresolved externals
* Linking errors *
c:\_vmsdata\FWH64\fwh64\samples>
Regards,
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
-
- Posts: 1102
- Joined: Mon Oct 17, 2005 5:41 am
- Location: Belgium
- Contact:
Re: FWH64
Running the demo adoxbr01.prg give this error log
Code: Select all
Application
===========
Path and name: c:\_vmsdata\FWH64\fwh64\samples\adoxbr01.exe (64 bits)
Size: 4,205,568 bytes
Compiler version: Harbour 3.2.0dev (r1603082110)
FiveWin Version: FWH 16.02
Windows version: 6.1, Build 7601 Service Pack 1
Time from start: 0 hours 0 mins 0 secs
Error occurred at: 24-03-2016, 14:27:38
Error description: Error BASE/1004 No exported method: EXECUTE
Args:
[ 1] = U
[ 2] = C CREATE TABLE CUSTSMAL (
ID AUTOINCREMENT PRIMARY KEY,
CUSTNAME VARCHAR( 30 ),
MARRIED BIT,
AGE BYTE,
SALARY MONEY
)
Stack Calls
===========
Called from: .\source\function\HARBOUR.PRG => EXECUTE( 0 )
Called from: adoxbr01.prg => CREATETABLE( 55 )
Called from: adoxbr01.prg => MAIN( 25 )
Regards,
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Re: FWH64
Antonio,
When I downloaded the FWH 64, I installed it into the folder FWH64. Thus I have two separate resources, FWH for 32 bit, FWH64 for 64 bit.
In the Samples folder for 64 bit, you have a Tutor02 build for Visual Studio. I started working with that assuming it would be a great place to start. Unfortunately there are problems.
1) The sample is setup for 32 bit construction.
2) The sample wants to link in files from the 32 bit Windows Kits 8.0 folder, but none of those files exist on the computer.
So, I modified the project files to point to the 64 bit files. Of course, without the Windows Kits .lib files, we can't build it.
Might I suggest you make the samples in the Make file generic, ie. name the folder FWH64 not FWTeam. Also, I created a Harbour64 folder for those libs.
My immediate need is for the files in the Windows Kits 8.0 folder ( x64 subfolder for 64 bit builds ). My install of Visual Studio 2015 Community is a Full install so I have all that Microsoft provides. Where did you go for the extra files ?
Tim
When I downloaded the FWH 64, I installed it into the folder FWH64. Thus I have two separate resources, FWH for 32 bit, FWH64 for 64 bit.
In the Samples folder for 64 bit, you have a Tutor02 build for Visual Studio. I started working with that assuming it would be a great place to start. Unfortunately there are problems.
1) The sample is setup for 32 bit construction.
2) The sample wants to link in files from the 32 bit Windows Kits 8.0 folder, but none of those files exist on the computer.
So, I modified the project files to point to the 64 bit files. Of course, without the Windows Kits .lib files, we can't build it.
Might I suggest you make the samples in the Make file generic, ie. name the folder FWH64 not FWTeam. Also, I created a Harbour64 folder for those libs.
My immediate need is for the files in the Windows Kits 8.0 folder ( x64 subfolder for 64 bit builds ). My install of Visual Studio 2015 Community is a Full install so I have all that Microsoft provides. Where did you go for the extra files ?
Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
-
- Posts: 1102
- Joined: Mon Oct 17, 2005 5:41 am
- Location: Belgium
- Contact:
Re: FWH64
Tim,
For me they are in "c:\Program Files (x86)\Windows Kits\8.1" after installing VC2015.
For me they are in "c:\Program Files (x86)\Windows Kits\8.1" after installing VC2015.
Regards,
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
Marc
FWH32+xHarbour | FWH64+Harbour | BCC | DBF | ADO+MySQL | ADO+MariaDB | ADO+SQLite
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: FWH64
Tim,
Simply go to FWH\samples and do:
build64.bat tutor02
If you have VSC2015 installed, then it will work fine
Simply go to FWH\samples and do:
build64.bat tutor02
If you have VSC2015 installed, then it will work fine
Re: FWH64
Antonio,
First, I do have 2015 installed.
Second, the build references Studio 2013, not 15. ( v12.0 not v14.0 )
Most important, it has two missing externals:
__stdio_common_vfprintf
__acrt_iob_func
If I change build64.bat to use V14.0 I still get the same errors.
Also, this does not resolve the missing externals that I mentioned when trying to build with VS 2015 IDE which is the real objective. I did all of that with the make file you supplied for the VS IDE ...
Tim
First, I do have 2015 installed.
Second, the build references Studio 2013, not 15. ( v12.0 not v14.0 )
Most important, it has two missing externals:
__stdio_common_vfprintf
__acrt_iob_func
If I change build64.bat to use V14.0 I still get the same errors.
Also, this does not resolve the missing externals that I mentioned when trying to build with VS 2015 IDE which is the real objective. I did all of that with the make file you supplied for the VS IDE ...
Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: FWH64
Tim,
I email you the FWH 64 libs for VSC2015
I email you the FWH 64 libs for VSC2015
Re: FWH64
Antonio,
Please, using the FWH 64 bit version, with 2015 VS set in the build64.bat file, try to build tutor02.prg in the \samples folder
Now, in addition to the other two missing items listed above, I also have a missing external
void__ ccdec1 which is called from ACTX.obj in FiveHC64.lib
This is using the build64.bat file you supply in the FWH 64 install under samples, except I have changed the call to V14.0 from V12.0 for the visual studio lines.
See how it compiles for you. I tried Tutor02.prg because initially I wanted to build with the IDE and that is the sample you used in the Make folder.
Again, I'm using the command line .bat file as you originally suggested.
Tim
Please, using the FWH 64 bit version, with 2015 VS set in the build64.bat file, try to build tutor02.prg in the \samples folder
Now, in addition to the other two missing items listed above, I also have a missing external
void__ ccdec1 which is called from ACTX.obj in FiveHC64.lib
This is using the build64.bat file you supply in the FWH 64 install under samples, except I have changed the call to V14.0 from V12.0 for the visual studio lines.
See how it compiles for you. I tried Tutor02.prg because initially I wanted to build with the IDE and that is the sample you used in the Make folder.
Again, I'm using the command line .bat file as you originally suggested.
Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: FWH64
Tim,
These unresolved externals from which modules are called ?
__stdio_common_vfprintf
__acrt_iob_func
These unresolved externals from which modules are called ?
__stdio_common_vfprintf
__acrt_iob_func
Re: FWH64
__acrt_iob-func called from:
hbvm.lib (hvmall.obj)
hbcplr.lib ( hbcomp.obj)
hbpp.lib ( ppcore.obj)
__stdio_common_vfprintf
hbpp.lib ( ppcore.obj)
hbcplr.lib ( hbcomp.obj, genc.obj, compi18n.obj, gencc.obj)
FiveH64.lib( prv2pdf.obj )
hbrtl.lib( errintlo.obj )
hbvm.lib ( hvmall.obj )
hbcplr.lib ( hbmain.obj)
void __cdec1
FiveHC64.lib ( GDIPLUS.obj, ACTX.ob )
fatal error LNK1120: 3 unresolved externals
Here is the output:
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ 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 'tutor02.prg' and generating preprocessed output to 'tutor02.ppo'...
Lines 4544, Functions/Procedures 1
Generating C source output to 'tutor02.c'... Done.
tutor02.c
Microsoft (R) Windows (R) Resource Compiler Version 6.3.9600.17336
Copyright (C) Microsoft Corporation. All rights reserved.
FiveH64.lib(HARBOUR.obj) : error LNK2019: unresolved external symbol __acrt_iob_func referenced in function HB_FUN_FREOPEN_STDERR
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(genc.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(compi18n.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(gencc.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
FiveH64.lib(PRV2PDF.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbrtl.lib(errintlo.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(hbmain.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
FiveHC64.lib(GDIPLUS.obj) : error LNK2019: unresolved external symbol "void __cdecl operator delete(void *,unsigned __int64)" (??3@YAXPEAX_K@Z) referenced in function HB_FUN_GDIPLUSIMAGEMATRIXCUSTOM
FiveHC64.lib(ACTX.obj) : error LNK2001: unresolved external symbol "void __cdecl operator delete(void *,unsigned __int64)" (??3@YAXPEAX_K@Z)
tutor02.exe : fatal error LNK1120: 3 unresolved externals
* Linking errors *
hbvm.lib (hvmall.obj)
hbcplr.lib ( hbcomp.obj)
hbpp.lib ( ppcore.obj)
__stdio_common_vfprintf
hbpp.lib ( ppcore.obj)
hbcplr.lib ( hbcomp.obj, genc.obj, compi18n.obj, gencc.obj)
FiveH64.lib( prv2pdf.obj )
hbrtl.lib( errintlo.obj )
hbvm.lib ( hvmall.obj )
hbcplr.lib ( hbmain.obj)
void __cdec1
FiveHC64.lib ( GDIPLUS.obj, ACTX.ob )
fatal error LNK1120: 3 unresolved externals
Here is the output:
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ 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 'tutor02.prg' and generating preprocessed output to 'tutor02.ppo'...
Lines 4544, Functions/Procedures 1
Generating C source output to 'tutor02.c'... Done.
tutor02.c
Microsoft (R) Windows (R) Resource Compiler Version 6.3.9600.17336
Copyright (C) Microsoft Corporation. All rights reserved.
FiveH64.lib(HARBOUR.obj) : error LNK2019: unresolved external symbol __acrt_iob_func referenced in function HB_FUN_FREOPEN_STDERR
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol __acrt_iob_func
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(genc.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(compi18n.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(gencc.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
FiveH64.lib(PRV2PDF.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbrtl.lib(errintlo.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
hbcplr.lib(hbmain.obj) : error LNK2001: unresolved external symbol __stdio_common_vfprintf
FiveHC64.lib(GDIPLUS.obj) : error LNK2019: unresolved external symbol "void __cdecl operator delete(void *,unsigned __int64)" (??3@YAXPEAX_K@Z) referenced in function HB_FUN_GDIPLUSIMAGEMATRIXCUSTOM
FiveHC64.lib(ACTX.obj) : error LNK2001: unresolved external symbol "void __cdecl operator delete(void *,unsigned __int64)" (??3@YAXPEAX_K@Z)
tutor02.exe : fatal error LNK1120: 3 unresolved externals
* Linking errors *
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: FWH64
Tim,
If you have both VS2013 and VSC2015 installed on your pc, please uninstall VS2013
I know it sounds weird but it happened also to me
If you have both VS2013 and VSC2015 installed on your pc, please uninstall VS2013
I know it sounds weird but it happened also to me
Re: FWH64
Antonio,
I RESOLVED the problem. The build64.bat file you provided was pointed to Visual Studio 12.0, but community is 14.0. I changed the first part of each line to 14.0, but not the second reference, so it was actually activating 12.0. When I changed the second part of the lines to 14.0, it builds.
Now, here is something else. I first did this on my Surface Book which only has Community 2015 installed. However, on my main machine, I have both 2013 and 2015 installed. ( 2013 is Visual Studio Professional ). When I made the change on the main computer, it also fixed the problem and works.
Maybe If you have Community 2013 you have to uninstall it for 2015, but in my case with 2013 PRO, I can also have 2015 installed and working.
My next task is to now get this to work in the IDE of Visual Studio 2015. With the build.bat working, it shows the files I need to link in. Now I will set 2015 up for those same files and see what happens.
Tim
I RESOLVED the problem. The build64.bat file you provided was pointed to Visual Studio 12.0, but community is 14.0. I changed the first part of each line to 14.0, but not the second reference, so it was actually activating 12.0. When I changed the second part of the lines to 14.0, it builds.
Now, here is something else. I first did this on my Surface Book which only has Community 2015 installed. However, on my main machine, I have both 2013 and 2015 installed. ( 2013 is Visual Studio Professional ). When I made the change on the main computer, it also fixed the problem and works.
Maybe If you have Community 2013 you have to uninstall it for 2015, but in my case with 2013 PRO, I can also have 2015 installed and working.
My next task is to now get this to work in the IDE of Visual Studio 2015. With the build.bat working, it shows the files I need to link in. Now I will set 2015 up for those same files and see what happens.
Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
Re: FWH64
Antonio,
I need 64 bit versions of the following files:
ace32.lib ( which I suppose would be ace64.lib ? )
hbssl.lib
hbtipssl.lib
rddads.lib
This is for MSVC Community 2015.
Tim
I need 64 bit versions of the following files:
ace32.lib ( which I suppose would be ace64.lib ? )
hbssl.lib
hbtipssl.lib
rddads.lib
This is for MSVC Community 2015.
Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019