VS, how to add library directories, include directories, and rely on-----go

at Build time, you may need to build some artifacts first to generate executable code that is used by other projects. Use project dependencies , Common Properties , Solution Property Pages dialog Box sets the current build order. To access this dialog box, in Solution Explorer , select a solution, select Property Pages on the View menu , and then select Project dependencies under Common properties. ".

about Project dependencies

When one project uses the executable code generated by another project, the project that generates the code is called the project dependency of the project that uses that code . As long as a project dependency has not been built, or has been modified since the most recent build, you should build the project first to generate and update the code that you want to use.

For example, if Project B needs executable code generated by its project dependency project A, and project A has been modified since the last build, then project A should be regenerated before building project B. This allows the executable code provided by project A to be modified before it is made available to project B.

If Project A has not been modified since the last build, you do not need to regenerate the new project A. Build only Project B.

Some items may appear dimmed in a list of dependencies and their check boxes are cleared. These items cannot be selected because this creates a dependency loop (P1 relies on P2, and P2 relies on P1), which causes the build to stall.

Other items may also appear dimmed in the list of dependencies, but their check boxes are selected. These projects have been added by the integrated development environment and cannot be changed. For example, when you add a project reference from a Visual Basic project to another project, a build dependency is added automatically, and the dependency is removed only by removing the reference.

1. Add lib files required for compilation (dependent)

Additional dependencies, input---add-on connectors, properties, configuration Properties, Solution Explorer, projects, and more lib are separated by spaces. (equivalent to "#pragma comment (lib," Winsock.lib ")" statement)

2. Add library (Libs) file directory

Method 1:[(Solution Explorer], properties, configuration properties, connector, general, add-in library directory
Method 2:[Menu] Tools, Options, projects and Solutions->c++ directory, select the appropriate platform, and then add the required library files directory

3. Add a directory containing (include) files

Method 1:[Solution Explorer] project, properties, configuration Properties->c/c++-> general, additional include directories
Method 2:[Menu] Tools, Options, projects and Solutions->c++ directory, select the appropriate platform, and then add the required "Include files" directory

VS, how to add library directories, include directories, and rely on-----go