Antonio: Differences between BORLAND and VCC

[byte-one]

1. If i use cGetDir(..) and choose a USB-drive for camera-cards BUT WITHOUT any inserted camera-card, the programm crashes in some times!
2. When using shadow() in MS-VC the shadow are bigger then in Borland and on some dialogs the wide (height?) of the dialog are cutting a little on right(bottom?) side.

[Antonio Linares]

Günther,

1. Please check if a hb_out.log file is created

2. Check the manifest files embedded into the EXE

[byte-one]

Antonio, from the first point the hb_out.log:

Application Internal Error - C:\WGUN\GUN1\gun32.exe
Terminated at: 2018-04-23 14:22:53
Unrecoverable error 9015: Symbol item expected from hb_vmDo()
Called from ASCAN(0)
Called from OWNDFROMHWND(3695) in .\source\classes\WINDOW.PRG
Called from FWSKINBTNPAINT(72) in C:\prg_allgemein\skins.prg
Called from FWSKINBTNFOCUSED(363) in C:\prg_allgemein\skins.prg
Called from CGETDIR(0)

On second point: Same manifest in MS-VC and Borland

[byte-one]

In the meantime i made some tests. No referring with ::shadow!
Please see the picture. On left side compiled with MS-VC, on right side compiled with Borland. It seems, only on dialogs from code!?

Code: Select all  Expand view

function dlg_test()
local oDlg, oFont, oMemo, oFile, oBtnok, oBtncancel, cFile := space(50), uTemp := " "
DEFINE FONT oFont NAME "Ms Sans Serif" SIZE 0, -10
DEFINE DIALOG oDlg FROM 50, 50 TO 250, 450 PIXEL TITLE "Test" FONT oFont
   @ 4, 3 GET oMemo VAR uTemp MULTILINE OF oDlg PIXEL SIZE 100, 100 FONT oFont
   @ 0, 0 GET oFile VAR cFile OF oDlg PIXEL SIZE 100, 12 FONT oFont
   @ 0,0 BUTTON oBtnOk PROMPT "OK" SIZE 46, 13 ACTION oDlg:End()
   @ 0,0 BUTTON oBtnCancel PROMPT "&Zurück" SIZE 46, 13 ACTION oDlg:End()
   ACTIVATE DIALOG oDlg;
      ON INIT (  ;
                oMemo:SetSize( oDlg:nWidth() - 17, oDlg:nHeight() - 77 ),;
        oMemo:SetSel( 0,0 ), ;
                oFile:nTop      := oDlg:nHeight() - 64,;
                oFile:nLeft     := 6,;
                oBtnOk:nTop      := oDlg:nHeight() - 64,;
                oBtnOk:nLeft     := oDlg:nWidth() - 197,;
                oBtnCancel:nTop  := oDlg:nHeight() - 64,;
                oBtnCancel:nLeft := oDlg:nWidth() - 104;
                 )
   oFont:End()
return NIL

[Antonio Linares]

Please inspect both EXEs using this tool:

https://bitbucket.org/fivetech/fivewin-contributions/downloads/peinfo.exe

look for differences in the embedded manifest files and/or resources

[Antonio Linares]

1. looks like memory corruption

[byte-one]

Thanks Antonio.
1. The error is present on all machines.
2. I inspect the files with PE but no differences. I compile with the exact same RC-File. Have you tested the code?

[byte-one]

Any news?
I found also that in dialogs from resource the height of the caption-area between MS-VC and Borland are different. Maybe different constants in the header-files from the compilers? For the moment i cannot use MS-VC.

[Antonio Linares]

We are checking it but can't see where the difference comes from yet

[byte-one]

Hello to all. I not can found any reason for the differences on the both compilers. Can please several from us test the above code with VCC and report!?

[cnavarro]

Gunther, I tested your sample also and I continue to investigate why

[Rick Lipkin]

To All

I have tried to create a script to compile MSVC 2017 using BuildxM ( xHarbour ) as my guide ( as you may remember ), unfortunately I gave up because I could not get any script or suggestions from the forum to cleanly compile tutor01.prg.

If anyone could post a working MSVC\xHarbour script .. I would be glad to help in comparing the difference between the two compilers.

Rick Lipkin

[TimStone]

Rick,

I do not use Borland, but I do create two builds of my primary application.
1). xHarbour ( .com / xBuilder with Pelles C ) using the version from 11/2015
2). Microsoft Visual Studio 2017 with Harbour libraries

Option 1 is only used by people who have ADS Version 7 or 8 and I have the proper libs for those in xHarbour.
Option 2 is for everyone else.

I have never tried Microsoft Visual C++ with xHarbour. I once was going to and was told there were no MSVC compatible libraries available for the commercial product.

I can assure you that Harbour and Microsoft Visual C++ work very well with FWH, and almost all of my clients use that version.

I should note: Visual Studio Community 2017 is FREE and quite capable of building any application. Antonio provides Harbour also for free. If you were to go that route, you would have no problem getting up and running. I actually do the builds in Visual Studio, and you can actually incorporate your editor of choice in the IDE ( I use UE Studio ).

Tim

[Rick Lipkin]

Tim or Anyone

I have downloaded the MSVC2017 32 bit Command line Compiler ( from Mel's site .. you do not need to install Visual Studio )



And the matching xHarbourM for MSVC2017


I would appreciate if anyone has a batch file ( like buildxm.bat ) to be able to compile tutor01.prg ... here are my file locations:

c:\MSVC2017
c:\Fwh1707
c:\XharbourM

Thanks
Rick Lipkin

[vensanto]

compiled with Harbour + Fivewin 18.03 and GCC 7.3 32 bit



compiled with Harbour + Fivewin 18.03 and GCC 7.3 64 bit


regards