Quote Originally Posted by fullmetalcoder View Post
A .pri file is not simpler than a prf .... Indeed, it forces the coder to add manage one more file and to make sure it is compatible with the "backend"... Using a prf "globally" (i.e. installed at the same time your preprocessor is, and in a standard location make it simpler for someone to use your framework without having to bother about potential internal breaks (for example in the CLI of your preprocessor...). And as I said already, it is more natural to most Qt users to add an extra config feature than to rely on the include() directive.
The way I have it set up, they would install chainlink and set the CHAINLINK_DIR environment variable on their system. Then they just need to add a single include statement at bottom of their .pro file:

Qt Code: 
  1. include($$(CHAINLINK_DIR)/chainlink_engine.pri)
To copy to clipboard, switch view to plain text mode 

I agree that a configuration option is more natural... however there are two important advantages of the .pri system in my situation:
1. If they upgrade Qt they will need to reinstall the prf (whereas with current system it will just work.
2. If they desire to see what's going on behind the scenes (because they are programmers after all), it will be easy to follow the "include" statement. After all, the .pri is only four lines (see a previous post)!