I am working on moving a number of projects from C++Builder 32 bit to bcc64x using RADStudio 13.1 - latest version of TMS VCL UI Pack installed using Smart Setup. Most of the projects use webupdate component. I am getting the above error.
To narrow the issue and replicate the error, I created a new Windows 64-bit (Modern) VCL project, added TMS WebUpdate component to the form and tried to build project. I get the same error as above: [ld.lld Error] ld.lld: error: could not open 'libssh2.lib': no such file or directory
there is only one libssh2.lib file on my dev computer in the directory \Products\tms.vcl.uipack. I copied the file to the \Products\tms.vcl.uipack\packages\d13\Win64x\Release directory. then I got this error: [ld.lld Error] ld.lld: error: \Products\tms.vcl.uipack\packages\d13\Win64x\Release\libssh2.lib: unknown file type
I figured that was not going to work because libssh2.lib is the 32bit library - but I tried it anyways. I am not sure why bcc64x compiler is looking to link libssh2.lib. I am guessing it needs to link the 64-bit libssh2 library. libssh2.a?
What do I need to do to fix this?
On a related note: I need to manually copy the libssh2.lib file to the \Products\tms.vcl.uipack\packages\d13\Win32\Release directory after every VCL UI Pack update for the 32bit projects to link.
I spent over an hour looking for info about this in tms support. I will create the lib and test tonight.
Are you planning on having the bcc64x libraries included in future versions of the components? I am assuming that it is something that can be done by Smart Setup.
Also, what about the issue that the libssh2.lib file is not being put in the appropriate directory by Smart Setup during the VCL UI Pack installation.
The folder
\Products\tms.vcl.uipack\packages\d13\Win32\Release
contains the binaries for .pas files that get compiled during install.
libssh2.lib is not getting compiled, hence it is not output to this folder.
Not sure if we can make it copy to this folder and not sure if it makes sense to copy it there. It is recommended to deploy libssh2.lib along with your app exe. So, as you won't be deploying the entire
\Products\tms.vcl.uipack\packages\d13\Win32\Release folder, it makes it easy to overlook deploying libssh2.lib if it would pickup the file from there on the developer machine anyway.