Bobcares

Qmake Shadow Build Directory | Guide

by | Aug 14, 2023

Learn how to use a Shadow Build directory Qmake. Our Server Management Support team is here to help you with your questions and concerns.

How to use a Shadow Build directory with Qmake

In Qt, we can use a shadow build directory with Qmake to separate the build output files from the source files in a distinct directory. In fact, this is also known as an “out-of-source” or “out-of-tree” build.

How to use a Shadow Build directory with Qmake

According to our experts, when we work on a software project via the Qt framework, we have source files and build output files related to the project.

Usually, projects are built by creating the build files and executables in the same directory as the source files. However, with a shadow build directory, we can keep the build output separate from the source files. This offers several benefits.

Benefits of using a shadow build directory

  • When the build files are in a separate directory, it keeps the source directory clean and organized.
  • It is easier to clean up the build output without affecting the source files. If we need to start fresh, you can delete the entire shadow build directory and create a new one.
  • With shadow build directories, we can create multiple build configurations for the same source files. This allows us to build the project with different build settings.
  • Keeping build artifacts separate is useful for version control systems like Git.

How to use a Shadow Build directory with Qmake

  1. First, we have to create a new directory outside of the source directory. This will be the shadow build directory.
  2. Then, we have to head to the shadow build directory and open a terminal to run qmake with the path to our project’s .pro file as seen below:

    qmake /path/to/source/project.pro

  3. Now, Qmake will generate the build files in the shadow build directory.

After that, we have to use a build tool like make or nmake to build our project.

After the build is successful, we can find the binary executable in the shadow build directory and run it from there.

At the end of the day, the shadow build directory, maintains a clear separation between our project’s source files and the build output.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In summary, our Support Techs demonstrated how to use a Shadow Build directory with Qmake.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF