title: Configuring Qt builds with Jenkins
body: <p>I have several Qt projects that are dependent upon a Qt library that I've developed.
  The project files (.pro) for projects which use the library define the LIBS and PRE_TARGETDEPS paths. For example: -</p>
  <blockquote>
  <p>PRE_TARGETDEPS += ../ProjectLibrary_Qt_5_2_1_clang_64bit-Debug/projectlibrary.dylib</p>
  <p>LIBS += -L../ProjectLibrary_Qt_5_2_1_clang_64bit-Debug -lProjectLibrary</p>
  </blockquote>
  <p>As you can see, there is a defined path to the linked library and they have been building with Shadow Builds, via Qt Creator. The file hierarchy is like this: -</p>
  <ul>
  <li>Projects
  <ul>
  <li>ProjectLibrary_Qt_5_2_1_clang_64bit-Debug
  <ul>
  <li>ProjectLib.dylib (the built library)</li>
  </ul>
  </li>
  <li>DependentProject
  <ul>
  <li>DependentProject.pro</li>
  </ul>
  </li>
  </ul>
  </li>
  </ul>
  <p>(dylib is an OSX extension, but it could equally be .lib for Windows, or .so for linux)</p>
  <p>However, Jenkins creates a different folder structure:-</p>
  <ul>
  <li>jobs
  <ul>
  <li>ProjectLib
  <ul>
  <li>workspace
  <ul>
  <li>Project.dylib</li>
  </ul>
  </li>
  </ul>
  </li>
  <li>DependentProject
  <ul>
  <li>workspace
  <ul>
  <li>DependentProject.pro</li>
  </ul>
  </li>
  </ul>
  </li>
  </ul>
  </li>
  </ul>
  <p>Now there is an extra directory (workspace), which would need this reflected in the .pro file and the names of the folders are different.</p>
  <p>Obviously, If I just call qmake on the .pro with a Jenkins build, the path to the library is going to be wrong.</p>
  <p>So, do I need to create a separate .pro just to be able to reflect the paths when building with Jenkins, or is there another way to handle specifying the location of libraries in the project file, for Jenkins, without having to change the directory structures?</p>