Re: Successfully merged projects

[John W. Eaton]

On 11-Apr-2011, John Swensen wrote:

| I think we can incorporate qmake into the regular Octave autotools, but qmake 
definitely makes some things easier.  For example, qmake already handles making 
MOC files and dealing with making an app bundle for OSX platforms. This 
encompasses a lot of rigamarole if attempted through autotools (I think). The 
point is that we would have to figure out how to do a bunch of stuff the 
"autotools way".  Is there something wrong with having an autotools target that 
calls
| 1) qmake in the UI directory
| 2) make in the UI directory
| We already need QT to even build the thing and qmake is distributed with QT, 
so it isn't as if we are adding another dependency.

I would like to avoid a recursive invocation of Make.  It is
preferable to have the top-level Makefile know everything about how
the project is built.  That way all the dependencies can be specified
more precisely.  I would also prefer to avoid mixing CMake and/or
qmake into the build process.

jwe