I'd like to know the answer to that too. I usually just locate the *.pas file in question and add the search path to project->options.
Todd. On Tue, 29 Aug 2006 17:54, [EMAIL PROTECTED] wrote: > This one bites me every time I install some third-party demo which > has a dependency on a package I don't normally install. > > So, let's see if I can get an easy solution, and remember it. > > Let's say I know I need the TXMLDocument component, which I don't > have installed. From the help, I can quickly find it is in the XMLDoc > unit. > > BUT -- is there some *easy* way to tell what furschinluggin' BPL I > need to install to make that unit and its components available? > > Hard ways, I've found, such as grepping for the unit name in the BPLs > -- but in this case, it's referenced in a whole bunch, so it doesn't > help. > > I find this whole "it depends on it but you can't find it" issue one > of the biggest timewasters when learning new areas of Delphi. So > there's probably an easy solution I haven't encountered in the past > decade. > > cheers, > peter > > > _______________________________________________ > Delphi mailing list > [email protected] > http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
