Delphi is so fast, because can use third-party control very much, but after the extensive use of third party controls, problems are also very much, for example, when we do dynamic library development, in order to compile the dynamic library (DLL) smaller, we generally compile time, choose to take package compiled, at that time, the control relies on BPL package together just go to the copy to the client computer, with control more and more, the package files are more and more, and a small program, itself is only a little big, in order to run normally, to copy all the packages in the past, cause our program as a whole is very large, we have been for this thing, and because developers always want their program can try to small,
Later, I found the Build on the Project - Options - packages if hook With the Runtime packages here, here, Delphi default is to load all support package, such as don't need such as FastReport package (fs7; Frx7; Frxcs7; FsDB7; FrxDB7; FsBDE7;) Are inside, under normal circumstances, the inside to remove the unwanted packages, recompile, can solve the problem,, but the back of the problem came out again, our company's development team, and under normal circumstances, very few people go to care what everyone to control development, each person's products rely on BPL package, in this way, people to manage to filter the BPL, alone in the actual development, it is not realistic, and then I continue to study, I found that Delphi after compiling, in the Project - Information for (engineering), and the BPL have this Project use package, and if you create a new Project, even inside the package (.bpl.bpl Rtl70, VCL70, VCLX70 BPL), also said, Delphi after compiling, know where rely on package, and the problem in this way, we are going to release or bad, compile a system may have dozens of package, we packed, can't check one by one, and even if one by one check, it would probably have to be wrong, resulting in the customer machines because of a lack of BPL package, so we have to wrap it's no use hundreds of all packaged together to release!!!!!
Hope can put all of the necessary before Delphi compiler BPL bag, can let the development can quickly find, filter depend on the bag, all don't need to pack out! Thank you very much! Hope ace can improve the valuable advice, I would appreciate!!!!!

CodePudding user response:

Go online to download the Depends tool, it can analyze dependencies, and then you can change based on the basic function of your

CodePudding user response:

It is good to do not need to directly?

CodePudding user response:

The building Lord instructions question wrong:
Build With the Runtime packages
1, if you don't choose, Delphi will automatically judge, packaging related BPL file into an EXE file,
2, if you choose, Delphi will specify packaging BPL file into an EXE file,

CodePudding user response:

reference lyhoo163 reply: 3/f

the building indicating the problem of incorrect:
Build With the Runtime packages
1, if you don't choose, Delphi will automatically judge, packaging related BPL file into an EXE file,
2, if you choose, Delphi will specify packaging BPL file into an EXE file,

Do you use Delphi packing tools can be loaded

CodePudding user response:

This can only artificial management, change the way of thinking: if you release procedure don't even know myself to release which packages, that hard to believe that you have good quality