Installtion tools abound. Use google. Innosetup has been the best I found (free too).
All of them require a skirmish with scripting. > Hi Steward, > > Thanks for your reply. What kind of installation tools you are > refering to when you say "Installation can add to the path setting"? > That would be exactly what I am trying to accomplish. > > Emmanuel > > --- In [email protected], [EMAIL PROTECTED] wrote: >> >> Define "static loading". >> >> The ones that are not loaded dynamically by you at runtime must be > in the >> current dir or on the path. >> >> Installation can add to the path setting. >> >> Same folder as the executable is easiest, but then you must ensure > the >> "working folder" is set for any shortcuts. >> >> The basic rules are given by Windows SDK in the discussion of > deploying >> DLLs. A bpl is just a Delphi-flavoured dll. >> >> As I recall (D5), there is no ideal easy solution. You either work > within >> the Windows rules or you code all your own loading. >> >> >> >> >> > Hi Guys, >> > >> > What would be an ideal location where to deploy bpl files for > static >> > loading? I don't want to use one those windows system folders and > would >> > prefer to update the system Path to include a location within my > app >> > environment, if such operation is at all possible. I was thinking > of >> > deploying my bpl's in a sub-directory under the application root >> > folder. Only I don't know how to make the application aware of > that sub- >> > folder. Any suggestions welcome. TIA. >> > >> > Emmanuel >> > >> > >> > >> > > >
