Dear Rob and Stephen, Thanks a lot. It worked.
I started first with that unit that I added in all my projects years ago. Then I started to make my own VCLs, one by one, I added the unit also there and I end up with this big package. But today (it took me hours) I cleaned up, splitting everything in small packages. Thanks again. ________________________ Rob Kennedy wrote: > Stephen Posey wrote: > >> 1. You don't need to actually include PersonalUnit.pas in the package Unit >> list, as long as it's visible on the Package Project's search path it will >> still be available. >> > > If any unit in the package uses PersonalUnit, then PersonalUnit must be > accounted for in the package. It must either be contained by the package > directly, or it must be contained in some other package that the first one > requires. Merely being on the search path isn't sufficient; the package > needs to know where it's going to find that unit at run time, and DCUs > aren't used at run time. > > If a unit isn't accounted for in one of the two mentioned ways, then the > compiler will implicitly include the unit in the package when the package > gets compiled. The compiler issues a warning when this happens, and it's a > warning that must never be ignored. > > As an isolated incident, it's not too bad to have a unit included > implicitly, but if the same unit gets implicitly included into more than > one package, then those two packages cannot be loaded simultaneously in > the same program. When the compiler warns that a unit has been included > implicitly, either add the unit explicitly, or find the package the unit > is already in and add it to your package's "requires" list, and then > recompile your package. > > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
