How does Delphi install and configure third-party controls and deal with file not found
- Prompt message: [dcc64 Error] E1026 File not found: ‘***.res’
Positive solution: You should read the official installation instructions. For example, if you install and deploy TMS FlexCel Studio for VCL and FireMonkey ....exe automatically or manually, you should read the official installation instructions carefully. : http://www.tmssoftware.biz/flexcel/doc/vcl/guides/installation-guide.html
Note: The installation of some controls depends on the platform deployment. If necessary, please select the platform first:
Tools->Options Sub-platform Environment Options is selected, then select Delphi Options->Library under its platform
Make sure these paths exist in the first 5 lines below:
If you have executed the “delete invalid paths” button by mistake, this button is recommended to never execute it, you can delete it line by line if you don’t need it! Because of an error in Delphi, the entries containing the $(Platform) macro are displayed in gray as if they are invalid. Actually not! As shown in the figure above, for example, the display: $(BDSLIB)\$(Platform)\release is gray, but this is an important way to be able to compile from the command line (and find the “rtl” package)! If you delete invalid paths with the button “delete invalid paths”, Delphi will delete all paths with $(Platform), and you will have to manually restore them, otherwise you will not find the rtl package at runtime.
2.2.1. Deployment library path, what is library path?
Usually third-party controls will deploy their packaged library path under the path containing lib, libs, and package. So what is the library path? The library path is the path where you need to recompile build install controls when you manually install it, which contains its project files, necessary *.INC (reusable source files), *.RES (resource files); The folder of the lower-level sub-platform; if the author of the distribution control is unwilling to publish all the source code, the dcu files generated during compilation (and *.hpp, *.a files generated by BCB) will also be placed in them. .
You need to deploy these paths to the library path!
2.2.2. Note: library path <> source path
Do not add the source path and its sub-paths containing the source code to the library path, otherwise if your project references controls, they will be recompiled and built every time you compile, which will greatly reduce work efficiency!
3.Deployment search path
Purpose: to ensure that you can identify when referring to the unit in the control! At the same time you can track its source code!
Path: usually the source path and its subpaths under the control installation folder!
4.Optional path Debugging.dcus when debugging the project
Purpose: When you are debugging a project, you need to track those parts of the control that have no open source code, so that you can see the source code during debugging, just use this option:
Note: After debugging, please turn off this option when you release the project.