Jump to content
marcocir

Delphi 11.3 CEF4Delphi

Recommended Posts

Posted (edited)

Hi all.

 

After successfully installing CEF4Delphi on Delphi 12.1, same package in Delphi 11.3 raised an error at startup.

Now, every attempt to reinstall it on Delphi 11.3 results in the same error, specifically during the installation of the design-time BPL.

 

Clip4.thumb.png.cfdb36224779d4fe3c456bc9124fa288.png

 

Any help?
Thanks
Marco

 

 

Edited by marcocir
A much better english ;)

Share this post


Link to post
Posted (edited)
12 hours ago, marcocir said:

Hi all.

 

After successfully installing CEF4Delphi on Delphi 12.1, same package in Delphi 11.3 raised an error at startup.

Now, every attempt to reinstall it on Delphi 11.3 results in the same error, specifically during the installation of the design-time BPL.

 

Clip4.thumb.png.cfdb36224779d4fe3c456bc9124fa288.png

 

Any help?
Thanks
Marco

 

 

Looks like the design-time package in the D11 folder (22.0 is the folder for that version) is in fact the version for D12, that is, should be in the 23.0 branch. But it may also be the correct version but tries to load a run-time package from the wrong folder. That is a common problem if the packages are not named properly with a version tag (280 for D11, 290 for D12). Run-time packages are loaded using Window's search strategy for DLLs (since they are DLLs in fact), which includes searching folders on the PATH. If you have several RAD Sudio versions installed each will have its BPL folder on the path, so the search may find the wrong version of a package if they all have the same filename.

A possible cure is to move the run-time package in question to BIN folder of the matching Delphi version (where bds.exe resides), since Windows  searches that folder first. Another is to start the IDE not via the start menu links the installer created but from a batch (cmd) file where you first redefine the PATH to only contain the folders for this Delphi version.

 

Oh, and if you can rebuild the packages you can of course change the project options to use the proper version tags for the produced binaries.

Edited by PeterBelow

Share this post


Link to post

Thanks Peter! :classic_biggrin:

I only have one Delphi version per system and I didn't notice this issue.

Share this post


Link to post

I'm sorry for the delay.
Thank you Peter, now I understand a little better how Delphi packages work.
In fact the problem with Delphi 11 was PATH:  the version 22.0 folder contained the correct (D11) version of the design-time packages, but run-time ones had same name of D12 corresponding packages and... PATH did the rest.

So, today I was able to fix that issue, manually moving those run-time packages to Delphi correct version bin folder, as a workaround, and, after, rebuilding all "broken" packages with $(Auto) LIB suffix.

And thank you too Salvador, setting LIB suffix to $(Auto), last answer, was icing on the cake 😉

Many thanks to both.
Marco

 


 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×