Features
* Standalone
* Uses qmake
* Parse and generate pkgconfig files
* Easy to use
* Only depends on ruby
* Multi-platform
* Powerful and flexible
Use
To use it, just copy qonfigure.rb to your project root, you will need to define a simple Ruby script with the configure options called setup.rb:
--------------------
def configure(setup)
setup.qt >= 4.2
setup.add_option(:name => "a-dir", :type => "path",

setup.add_option(:name => "a-string", :type => "string",

setup.add_option(:name => "a-bool", :type => "bool",

setup.find_package(:name => "a-pkgconfig-package",

setup.add_option(:name => "some-dir", :type => "path",

setup.add_test(:id => "custom_test", :name => "Custom support", :custom => "int main() { return 0; }", :defines => ["HAVE_CUSTOM"],

setup.add_test(:id => "myfeature", :name => "My feature support", :defines => ["HAVE_MY_FEATURE"], :headers => ["myfeature.h"], :libs => "-lmyfeature",

end
--------------------
First time a setup.rb template will be generated.
Qonf uses frontends to get the options, currently it has two frontends implemented: tk (gui) and plain (console), tk is used by default if it is present in your machine. (see screenshots)
when the process is finished a file called "config.pri" will be generated, to use non-global features you will need to include that file in your .pro and link the features, for example:
--------------------
...
include(../config.pri)
link_with(a-pkgconfig-package) {
DEFINES += SOMETHING
}
link_with(myfeature) {
INCLUDEPATH += /something
}
...
--------------------
Ratings & Comments
0 Comments