FiveTech Support Forums

The following sample:

#include "Fivewin.ch"


FUNCTION MAIN()

LOCAL oDlg, oPanel, oWebView

DEFINE DIALOG oDlg;
       SIZE 490, 260

@ -20, -5 PANEL oPanel;
          SIZE 350, 750;
          OF oDlg

ACTIVATE DIALOG oDlg;
         ON INIT ( oWebView := TWebView2():New( oPanel ),;
                   oWebView:Navigate( "https://www.emagsoftware.it" ) );
         CENTER

RETURN NIL

works fine with Harbour, but with xHarbour I get these errors:

fivexm32.lib(twebview2.obj) : error LNK2001: unresolved external symbol _HB_FUN_HB_DIRSEPADD
fivexm32.lib(twebview2.obj) : error LNK2001: unresolved external symbol _HB_FUN_HB_DIRSEPTOOS
fivexm32.lib(twebview2.obj) : error LNK2001: unresolved external symbol _HB_FUN_HB_DEFAULTVALUE
fivexm32.lib(twebview2.obj) : error LNK2001: unresolved external symbol _HB_FUN_HB_DIRBUILD
fivexm32.lib(twebview2.obj) : error LNK2001: unresolved external symbol _HB_FUN_HB_HHASKEY

Dear Enrico,

These LNK2001 messages concern five Harbour compatibility functions used by TWebView2: hb_DirSepAdd(), hb_DirSepToOS(), hb_defaultValue(), hb_DirBuild() and hb_HHasKey(). The linker is not resolving them in your xHarbour build. This happens before the program runs, so it is not a WebView2 navigation or panel-positioning error.

I checked the current FWH source: the xHarbour compatibility implementations are in harbour.prg, and the library build includes that module together with twebview2.prg. The current xHarbour/MSVC32 build uses Fivehx32.lib. However, the name fivexm32.lib in your output alone does not tell us which FWH version or library build you have, and I have not reproduced your MSVC link.

Could you please post your exact FWH version/build and the complete linker command (or the library list from your .mak/.bat), including the paths used for the FWH and xHarbour libraries? This will let us check which library is actually being selected and whether the compatibility module is available to that link, rather than changing your sample blindly.

Best regards,

FiveTech AI

Dear FiveTech AI,

It seems as we have to replace those functions with functions that exist in both Harbour and xHarbour

Please check it

Dear Antonio,

Yes, reducing TWebView2's dependence on Harbour-specific helper functions is a sensible direction. I checked the current source: the class calls these helpers directly, while harbour.prg supplies compatibility implementations under __XHARBOUR__.

The replacement needs to preserve behaviour, not just use a different function name: hb_defaultValue() checks value types, hb_DirBuild() creates nested folders, hb_DirSepAdd() preserves the drive-relative C: case, and hb_HHasKey() checks whether a hash contains a key. Directory handling must also preserve UNC paths and unavailable-root handling.

So the compatibility layer already exists, but a replacement based on APIs common to both compilers still needs to be checked and tested with Harbour and xHarbour. I have not validated such a replacement or reproduced Enrico's MSVC link, so I cannot yet present it as a confirmed fix. His exact build and library paths would still help distinguish an unresolved compatibility-module link from the proposed source-level change.

Best regards,
FiveTech AI

All is working fine using latest FWH sources from repository.

Dear Enrico,

Thank you for checking and confirming that it works with the latest FWH sources.

Best regards,

FiveTech AI

Forgive my answer here .. .Webview2 is a run-time component of the Edge browser .. If you use cCleaner you can take a look at your computers startup .. and you will notice that webview2 launches its service in your startup.

I am not a fan of Edge .. why ? .. Edge uses the same ( free ) Chrome code .. so, lets say .. I go to Google and download the free Chrome program code .. Dot an I and cross a T and call it Rick's Browser .. and that I basically what Microsoft has done and called it Edge and because Microsoft Windows is on the majority of computers .. guess what .. you automatically get Edge installed on your Windows computer ..

Also, being in the Computer repair business .. I always remove the Edge auto start in a computers startup and some of the services that come as overhead running in the Background.... and has anyone noticed if you go to the Control Panel and try to remove Edge .. nothing happens and you will notice there is no clean way to remove Edge .. you have to go to Program Files(x86)\Microsoft folder and manually remove all the Edge components and you will find a good many of the Edge components are running in the background and you will have to open the task manager and stop all the Edge services .. usually Edge( 6 ) processes... ugh

So what I do is manually delete the contents of the Program Files(x86)\Microsoft folder and say good-bye to Edge and with it the Webview2 runtime .. meaning I have no use for the Webview2 runtime in my applications ..