Home/ Questions/Q 1030425
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T12:41:51+00:00

I contribute to a decent-sized C++ project with a number of dependencies. The problem

  • 0

I contribute to a decent-sized C++ project with a number of dependencies. The problem is, the project contains the source of all of its dependencies (e.g. pcre, zlib, etc.). I want to trim the project down to just what’s relevant to the program itself. Is there some relatively standard way to compile these libraries and put them somewhere, and have their header files also easily accessible?

For what it’s worth, I’m using Windows 7, and I’m developing using VS2005. I’m also a complete noob with working on large C++ projects on Windows; I’ve never really needed to step outside the standard library and win32.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A structure that we use on my workplace is having one “External” folder that contains an “Include” and a “Lib” folder for the headers and external Libs. However, as we also use VS, we try to use its “Dependencies” feature as most as possible, removing manual inputs to the linker. That means only projects that are not under the same solution goes to the “External” folder. Also, as we have some third-party libraries specific to some projects, we create folders inside the project folder for these includes and libs. This is how it gets:

    .\
|-Project1\ --> contains Project1.vcproj
|-Project2\ --> contains Project2.vcproj
| |-Third-Party\
|   |-Include\
|   |-Lib\
|-External\
| |-Include\
| |-Lib\
|-InternalLibrary\ --> contains InternalLibrary.vcproj
|-Solution.sln --> includes the vcproj's and link them as necessary by its dependencies

    I can’t tell if this is the best structure ever, but everything is under source control, we can do night builds just by building the solution, and development goes by building single projects.

    • 0