Support Windows 64-Bit (Modern) in the installer

Thermco Systems

Currently, to get support for the new 64-Bit C++ compiler, after installing LMD I have to open the project group, change all runtime packages to this target, and rebuild them all.

Could the installer be upgraded to supply prebuilt packages and libraries for this toolchain.

Thanks,

Andy

Eugene Balabuev (LMD)

We thinking about this. But, this is not fast to do.

Albert Wiersch

I'm trying to move over to the new C++ compiler as well (Windows 64-bit (Modern)). The installer creates 'Win32' and 'Win64' folders but not 'Win64x' for the new C++ toolchain.

Was sad to see this is an issue with so many 3rd party components.

Can this be supported ASAP?

Eugene Balabuev (LMD)

I've trying to achieve this currently.

Eugene Balabuev (LMD)

LMD 2024.6 release is published with the experimental support of the new Win64x platform. Use RAD Studio 12.1 or higher for this.

Albert Wiersch

Great news. I will give it a try soon.

Was going to throw this out in case it helps (similar problem/issue):

https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-2221

Albert Wiersch

Well, I installed SyntaxEdit 2024.6 and created a new C++ VCL project.

I was able to add a TLMDEditView and TLMDEditDocument to the form but it would not link (it did compile though).

Linker errors:

[ld.lld Error] ld.lld: error: could not open 'usp10.a': no such file or directory

[ld.lld Error] ld.lld: error: unknown file type: LMDSedView.o

[ld.lld Error] ld.lld: error: unknown file type: LMDSedDocument.o

I see 'Win32' and 'Win64' folders in '...\lib\d29\Win32' but no 'Win64x'.

If I switch to 'Windows 64-bit' from 'Windows 64-bit (Modern)' then it compiles and links.

Maybe I'll try the universal installer.

Albert Wiersch

Couldn't get it to work with the universal installer either. It's like it's installing 2024.5 instead of 2024.6. Is something wrong or not updated with the SyntaxEdit installers?

Eugene Balabuev (LMD)

Hi,

1) Only new universal installer supports Win64x. Old installers will not be changed to achieve this.

2) I tried installer from SyntaxEdit download area, selected only SyntaxEdit product. And Win64x folder was created. So, its definitely installs 2024.6 at my side. And the installer window caption (header) should include "2024.6" as well.

3) It may be true that some specific (not LMD) library, like 'usp10.a' creates link error, since the platform is new for us. I'll recheck it.

Eugene Balabuev (LMD)

As a workaround for now you can search for LMDSedView.hpp file in your Win64x libraries folder and remove "pragma link ups10.a" line.

Thermco Systems

The new 64-bit compiler (modern) produces libraries with the .LIB extension... Whereas the old 64-bit produces libs with .A as the extension.

It's by design - prevents trying to link the wrong library files...

Andy

Albert Wiersch

I went here:

https://user.lmd.de/customer/downloads/1997

And downloaded:

https://user.lmd.de/downloads/lmd2024vcl/lmdsetup.exe

When I run it, the title bar / window caption says "Setup - LMD VCL Components 2024.5".

Shouldn't it say 2024.6?

UPDATE: I added "?test" to the download link and got a "2024.6" installer so maybe there is some type of cache getting in the way of getting the updated file? Going to test it out now and try to get Win64x to work.

UPDATE 2: SUCCESS!!! After getting the 2024.6 installer, installing, and commenting out the '#pragma link "usp10.a"' line in LMDSedView.hpp it compiled and linked!

Albert Wiersch

UPDATE... I'm getting closer and closer to moving to Win64x but one major issue seems to be stopping me now and it seems to be the Addict spellchecked and LMD SyntaxEdit.

For some reason it works on Win64 but trying to perform certain Addict spell checking functions with an LMD edit component on Win64x cause a major crash.

The line that crashes is:

AddictSpell->CheckWinControl(Edit,Ad3spellbase::ctSmart);

Edit is an LMDEditView.

The top 3 lines of the Call Stack:

:00007FF6BC5F9112 Lmdsedview::initialization()()

:00007FF6BC5D4665 Lmdsedview::TLMDCustomEditView::EM_GetLine(Winapi::Messages::TMessage&)()

:00007FF6BC34A714 System::TObject::Dispatch(void*)()

The exception:

First chance exception at $00007FF6BC5F9112. Exception class 0xc0000005 with message 'Exception 0xc0000005 encountered at address 0x7ff6bc5f9112: Access violation writing location 0x46a00000'. Process chv.exe (29100)

So I'm wondering if this could be an issue with LMDEditView/SyntaxEdit with Win64x?

Debugging issues like this are 'above my pay grade'... hoping someone at LMD might have any ideas while I continue to investigate?

UPDATE: I made a sample/test app and am getting an AV with both Win64 and Win64x. Will post a separate message with more info and a link to my simple test app.

Eugene Balabuev (LMD)

Answered in another thread...