After adding a package as a dependency in another project, referral problems persist

Question

After adding a package as a dependency in another project, referral problems persist

Navigation

#1 by (3 votes)

3

Having created a package and soon after referencing it as a dependency on a project, which is in the same project group, I have problems trying to use the unit references contained in the package. Even after adding addiction.

Even after compiling and having the package installed, the error continues.

As this my project group structure and how I refer:

HereImarkthedependency:

I even browse to the directory indicated by the image ( C:\Users\Public\Documents\RadStudio.0\Bpl\ ) and there is the file ORM.bpl .

But when trying to use the units that would already be compiled in the package, I can not:

Thisistheerrorwhentryingtocompile:

Whenever I needed to associate the libraries of other packages, even though I installed them in the Delphi IDE, I always had to add unit in the project or folders browsed by Delphi ( Libraries ).

So I ask if in this type of case the dependency reference does not work at all and so what is the purpose of this reference?

Or, of course, if I did or did not do something?

delphi delphi-xe3 packages

asked by anonymous 13.10.2014 / 03:01

1 answer

Identify the Area, Controller, and Action of a View How popular is an array with the registered bank records?

score 3 · Answer 1

When you mark as dependency Delphi will only compile the ORM.bpl before it.

What you should do is add the DCP of the ORM package to Runtime packages . To do this, enter Options of your project and search for Runtime packages .

Remembering that if you are using a version Delphi XE or higher, you have to watch for Target .

One important thing, if you are trying to send the .bpl of the compiled file, you should check the option Link with runtime packages as True .