Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Packages files for Tokyo 10.2.2



Permlink Replies: 5 - Last Post: Feb 26, 2018 9:05 AM Last Post By: Remy Lebeau (Te...
Joao Lira

Posts: 40
Registered: 3/25/03
Packages files for Tokyo 10.2.2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 4, 2018 8:07 AM
Hello,

Currently, I am able to use Indy on Delphi Tokyo 10.2.2 if I stick to the version that comes with the default installation. There are no Delphi Tokyo packages if I download Indy from https://indy.fulgan.com/. Indy 'Indy240.groupproj' group project compiles ok on Delphi Tokyo 10.2.2, but raises an "Access Violation" error when I try to install the "dcl" components. Where can I get the correct Delphi Tokyo packages for Indy?

Thanks in advance.

Regards,
Joao Lira.

Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Packages files for Tokyo 10.2.2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 5, 2018 11:53 AM   in response to: Joao Lira in response to: Joao Lira
Joao Lira wrote:

There are no Delphi Tokyo packages if I download Indy from
https://indy.fulgan.com/.

That is because I have not checked in any packages for Tokyo into
Indy's SVN yet, as I don't have Tokyo installed to test with.

Indy 'Indy240.groupproj' group project compiles ok on Delphi Tokyo
10.2.2

Did you rename the packages to use 250 instead of 240? 240 is for
Berlin.

but raises an "Access Violation" error when I try to install
the "dcl" components.

What is the exact and complete error message? Have you tried debugging
the IDE with a second instance of the IDE to find out exactly where the
AV is coming from?

Where can I get the correct Delphi Tokyo packages for Indy?

At this time, from nowhere. You will have to create your own packages.

--
Remy Lebeau (TeamB)
Joao Lira

Posts: 40
Registered: 3/25/03
Re: Packages files for Tokyo 10.2.2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 7, 2018 7:26 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
Joao Lira wrote:

Did you rename the packages to use 250 instead of 240? 240 is for
Berlin.

No, I created a new project for Delphi Tokyo. It compiled all modules ok but it didn't install.

What is the exact and complete error message? Have you tried debugging
the IDE with a second instance of the IDE to find out exactly where the
AV is coming from?

I don't know how to do that debugging, but I'll try to get the full error message.

Thank you.

Regards,
Joao Lira.
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Packages files for Tokyo 10.2.2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 7, 2018 8:47 PM   in response to: Joao Lira in response to: Joao Lira
Joao Lira wrote:

I don't know how to do that debugging

Like I said, you can simply run one instance of the IDE inside the
debugger of another instance of the same IDE. Then the second instance
can debug the first instance like any other program.

--
Remy Lebeau (TeamB)
Salvatore Besso

Posts: 10
Registered: 5/10/00
Re: Packages files for Tokyo 10.2.2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 26, 2018 2:57 AM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
That is because I have not checked in any packages for Tokyo into
Indy's SVN yet, as I don't have Tokyo installed to test with.

At this time, from nowhere. You will have to create your own packages.

I have created the packages with 250 suffix and edited them accordingly but I have a problem with command line compilation. I use a self made batch file to accomplish this task.

First of all I have removed preinstalled Indy packages from IDE and renamed all preinstalled packages to <name.ext>.bak.

My batch files have usually always worked. It ignores any .dproj file because all needed definitions, declarations and settings are inside it.

This time, as soon as compilation starts I get this error:

IdAboutVCL.pas(25) Error: E2003 Undeclared identifier: 'TImage'

Among the various definitions, declarations and settings in my batch file there is:

set unitscopenames=Bde;Data;Data.Bind;Data.Cloud;Datasnap;Datasnap.Win;IB;FMX;FMX.ASE;FMX.Bind;FMX.Canvas;FMX.DAE;FMX.Filter;FMX.Platform;FMX.Printer;iOSapi;Macapi;Posix;System.MAC;System;System.Bindings;System.Generics;System.Math;System.Sensors;System.Tether;System.Win;Vcl;Vcl.Imaging;Vcl.Samples;Vcl.Shell;Vcl.Touch;SOAP;Web;Web.Win;Winapi;Xml;Xml.Internal;Xml.Win

This declaration has been desumed from the Delphi Wiki for Tokyo.

Well, with this long version I cannot compile with the above mentioned error. If I change this declaration with this short version:

set unitscopenames=System;System.Win;Vcl;Winapi

then command line compilation ends without errors.

Why this happens only with Indy? All other components that I compile with this batch file don't give any errors with the long version of unitscopenames.

The same problem happens since Delphi XE8, if I remember well.

Regards
Salvatore

Edited by: Salvatore Besso on Feb 26, 2018 2:59 AM
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Packages files for Tokyo 10.2.2 [Edit]
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 26, 2018 9:05 AM   in response to: Salvatore Besso in response to: Salvatore Besso
Salvatore Besso wrote:

I have a problem with command line compilation. I use a self made
batch file to accomplish this task.

Why do you need a command-line compile? Why not just compile and
install the packages from within the IDE itself?

This time, as soon as compilation starts I get this error:

IdAboutVCL.pas(25) Error: E2003 Undeclared identifier: 'TImage'

It should work, since IdAboutVcl.pas uses the ExtCtrls unit, which
defines TImage, and your list of unit scopes includes the 'Vcl' scope.

Well, with this long version I cannot compile with the above
mentioned error. If I change this declaration with this short version:

set unitscopenames=System;System.Win;Vcl;Winapi

then command line compilation ends without errors.

Obviously, you don't need to specify so many unit scopes, since Indy
doesn't use most of them anyway. You should be specifying only what
you actually need to compile.

Why this happens only with Indy?

I can't answer that.

--
Remy Lebeau (TeamB)
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02