[Qt-interest] How make Qt projects / Makefiles with no hard-coded paths?

Ed Sutton ESutton at fescorp.com
Mon Mar 29 22:37:39 CEST 2010


What are some best practices for building Qt projects that leave no hard-coded paths in the Makefile or Qt project files?

My goals are:


 1.  Retrieve project source from Subversion on any machine configured for development or building releases.
 2.  Build a release by running make in the project source using an un-modified version of the Makefile retrieved from Subversion ( no hard-coded paths in Makefile )
 3.  Be able to open and build an un-modified Qt project file retrieved from Subversion ( no hard-coded paths in the Qt project file )

I have not used QTDIR, PATH or QMAKESPEC environment variables before.  Is this the best way?

I do not mind requiring Qt to be installed to a specific path such as /opt/qtsdk-2010.02 or configured in a consistent manner.

Thank you for sharing your experiences.

-Ed





More information about the Qt-interest-old mailing list