Re: [CEDET-devel] EDE qmake based project

[Eric M. L. <eri...@gm...>]

On 04/19/2012 10:12 AM, Matthias Meulien wrote:
>
>     I typed qmake on my machine, and it did something, so I'm guessing
>     the best way to get help on the mailing list is to have some small
>     stock demo project we can run against that shows the kinds of
>     problems you are trying to overcome.
>
>
> I have attached a project taken from qmake tutorial.
>
> I guess I should use something like the following to have:
> (require 'ede-generic)
>
> ;;; QMAKE
> (defclass ede-generic-qmake-project (ede-generic-project)
>    ((buildfile :initform "hello.pro <http://hello.pro>"))
> "Generic Project for qmake.")
>
> ;; TODO Fix initialization of initform: *.pro?
>
> (defmethod ede-generic-setup-configuration ((proj
> ede-generic-qmake-project)
>                          config)
> "Setup a configuration for QMake."
>    (oset config build-command "qmake")
>    (oset config debug-command "gdb "))
>
> (ede-generic-new-autoloader "qmake-project" "qmake" "hello.pro
> <http://hello.pro>"
> 'ede-generic-qmake-project)
>
> ;; TODO Fix initialization of project file: *.pro?
>
> (ede-enable-generic-projects)
>
> How to initialize buildfile initform property and project file as they
> depend of the project name?

Hi,

Thanks for the example.

To solve the problem with *.pro, you can create a function, such as 
(untested):

(defun ede-generic-qmake-projfile (dir)
    "Is there a .pro file in the current directory."
    (car (directory-files dir nil "\\.pro$")))

and pass that into the generic autoloader instead of hello.pro.  I 
hadn't tried this with a generic project, but it should be ok.

The buildfile doesn't need to match, the important part is the argument 
passed into the autoloader.

In an earlier email you asked about shadow builds.  you can put any 
compound build command you want into the build-command.

Good luck
Eric