Warning, /kdevelop/kdevelop/plugins/qmakemanager/TODO is written in an unsupported language. File is not indexed.
0001 So the basic way of how I imagined this should work is: 0002 0003 a) run qmake to find out the place of the Qt installation, in particular 0004 the include, lib and plugin dirs and most importantly the mkspecs dir 0005 and which mkspec to use (possibly use-configurable). 0006 b) read and parse the .prf files from mkspecs/features, usually starting with 0007 qt_config.prf this will declare a lot of the QMake functions and they're 0008 implemented with qmake itself 0009 c) read and parse the files for the mkspec (qmake.conf, all the included 0010 files), this should produce a couple base variables 0011 d) start with the top-level qmake file from the project (this might 0012 again need user-specification via gui which file should be used) 0013 e) during parsing, evaluate all the known functions, so we automatically 0014 dive into include() directives, can do variable substitution and also 0015 the list-stuff qmake supports 0016 0017 That's the theory, what's there right now is a full qmake parser (no known 0018 bugs or missing features from qmake) and the start of some basic 0019 evaluation. I've actually started with the variable substitution. 0020