Entry Point Not Found, Can't load package |
|
Using the latest Indy build 5229, Delphi XE4 and Windows 7 64-bit Pro
Indy builds OK.
But when I restart XE4 with my project I get the following errors
bds.exe - Entry Point Not Found
The procedure entry point
@Idstackwindows@TIdStackWindows@AddLocalAddressesToList$qqrp23System@Classes@TStrings
could not be located in the dynamic link library IndySystem180.bpl
OK
Error
Can't load package c:\program files (x86)\embarcadero\rad
studio\11.0\bin\dclIndyCore180.bpl
Can't load package c:\program files (x86)\embarcadero\rad
studio\11.0\bin\dclMetropolisUILiveTile180.bpl
The specified procedure could not be found
Do you want to attempt to load this package the next time a project is
loaded?
Yes
The bds error repeats
OK
The package error repeats
Yes
The bds error repeats
OK
the package error repeats
Yes
and now XE4 is up and running.
If I then close it and restart it, the errors do not occur.
--
Bob Small
|
Re: Entry Point Not Found, Can't load package |
|
Remy Lebeau (TeamB) wrote:
>Robert wrote:
>
>> The procedure entry point
>> @Idstackwindows@TIdStackWindows@AddLocalAddressesToList$qqrp23System@Classes@TStrings
>> could not be located in the dynamic link library IndySystem180.bpl
>
>XE4 shipped with Indy 10.6.0.0. In that version, AddLocalAddressesToList()
>was declared as abstract in TIdStack and overridden in TIdStackWindow (and
>other descendants).
>
>Earlier this year (March 14 2014) in SVN revision 5105, TIdStack.GetLocalAddressList()
>was added, and the implementation of AddLocalAddressesToList() was moved
>into TIdStack directly and marked as deprecated. That is why TIdStackWindows.AddLocalAddressesToList()
>no longer exists. Whichever BPL is trying to link to TIdStackWindows.AddLocalAddressesToList()
>was compiled against the older IndySystem180.bpl file and would have to be
>recompiled to use your newer IndySystem80.bpl file.
I guess that the only way I would find out which BPL is the culprit
would be to go through disabling and enabling them one by one.
>
>> Can't load package c:\program files (x86)\embarcadero\rad studio\11.0\bin\dclIndyCore180.bpl
>
>Did you recompile Indy's design-time packages?
Yes, I did.
But since I don't use the design-time packages it probably doesn't
matter.
>
>> Can't load package c:\program files (x86)\embarcadero\rad studio\11.0\bin\dclMetropolisUILiveTile180.bpl
>
>That is a known issue and documented in Indy's install instructions:
OK. I don't use Live Tiles either.
Thanks Remy
--
Bob Small
|
Re: Entry Point Not Found, Can't load package |
|
Robert wrote:
> The procedure entry point
> @Idstackwindows@TIdStackWindows@AddLocalAddressesToList$qqrp23System@Classes@TStrings
> could not be located in the dynamic link library IndySystem180.bpl
XE4 shipped with Indy 10.6.0.0. In that version, AddLocalAddressesToList()
was declared as abstract in TIdStack and overridden in TIdStackWindow (and
other descendants).
Earlier this year (March 14 2014) in SVN revision 5105, TIdStack.GetLocalAddressList()
was added, and the implementation of AddLocalAddressesToList() was moved
into TIdStack directly and marked as deprecated. That is why TIdStackWindows.AddLocalAddressesToList()
no longer exists. Whichever BPL is trying to link to TIdStackWindows.AddLocalAddressesToList()
was compiled against the older IndySystem180.bpl file and would have to be
recompiled to use your newer IndySystem80.bpl file.
> Can't load package c:\program files (x86)\embarcadero\rad studio\11.0\bin\dclIndyCore180.bpl
Did you recompile Indy's design-time packages?
> Can't load package c:\program files (x86)\embarcadero\rad studio\11.0\bin\dclMetropolisUILiveTile180.bpl
That is a known issue and documented in Indy's install instructions:
http://www.indyproject.org/Sockets/Docs/Indy10Installation.aspx
{quote}
In D/CB/RAD XE3+, Embarcadero's Metropolis UI LiveTile framework is compiled
against the Indy 10 packages that ship with the IDE. Installing a new version
of Indy will render LiveTiles unusable, as it will not be able to load the
Indy packages anymore, and LiveTiles cannot be recompiled by end users.
If you need to use LiveTiles then you will need to maintain the original
Indy 10 packages for use in LiveTile projects. You can use a separate installation
of Indy 10 for non-LiveTile projects. This has not been addressed by Embarcadero
yet so Indy 10 upgrades and LiveTiles can co-exist.
{quote}
--
Remy Lebeau (TeamB)
|