Is it possible to use qmake to create a Makefile with more than one executable target in the same directory. Typically I like to create a test program for every class (a bit like including a public static void main( String args[] ) in every java class)? Comments on whether you think I should be using qmake at all are welcome. JDL -- Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
John Lamb writes:
Is it possible to use qmake to create a Makefile with more than one executable target in the same directory. Typically I like to create a test program for every class (a bit like including a public static void main( String args[] ) in every java class)?
Comments on whether you think I should be using qmake at all are welcome. JDL
I really don't think it is necessary to use it. I think it simplifies some tasks, but I think the functionality can be duplicated with make. I think the idea is you create a project file that details what is in the project and qmake uses this to build the targets. With make you will define your targets and then decide how to build them. I have noticed in qt that they try to do something like autoconf, automake do but much simpler, and I think qmake is a part of that. I wouldn't waste my time on learning it, and just learn the autoconf, automake stuff if you have a substantial enough project to warrant it. I think Troll's reason for doing it is to make life easier for companies who don't have people with make or system architectural expertise in house, but just want to port their windows applications to Unix.
* Jesse Marlin
John Lamb writes:
Is it possible to use qmake to create a Makefile with more than one executable target in the same directory. Typically I like to create a test program for every class (a bit like including a public static void main( String args[] ) in every java class)?
Comments on whether you think I should be using qmake at all are welcome. JDL
I really don't think it is necessary to use it. I think it simplifies some tasks, but I think the functionality can be duplicated with make. I think the idea is you create a project file that details what is in the project and qmake uses this to build the targets. With make you will define your targets and then decide how to build them.
Yes, but one have to learn make, which can be cumbersome in the beginning. It's really easy with qmake.
I have noticed in qt that they try to do something like autoconf, automake do but much simpler, and I think qmake is a part of that. I wouldn't waste my time on learning it, and just learn the autoconf, automake stuff if you have a substantial enough project to warrant it.
Where did you notice that? It's bogus. Qmake has nothing to do with automake and autoconf whatsoever. Did you ever use it? Please have a look at http://doc.trolltech.com/3.0/qmake-manual.html
I think Troll's reason for doing it is to make life easier for companies who don't have people with make or system architectural expertise in house, but just want to port their windows applications to Unix.
I've been using qmake a lot, and it's really nice. The above URL would help get you started. -- Mads Martin Jørgensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort?" -- A. P. J.
Mads Martin Joergensen writes:
* Jesse Marlin
[Jun 18. 2002 21:40]: John Lamb writes:
Is it possible to use qmake to create a Makefile with more than one executable target in the same directory. Typically I like to create a test program for every class (a bit like including a public static void main( String args[] ) in every java class)?
Comments on whether you think I should be using qmake at all are welcome. JDL
I really don't think it is necessary to use it. I think it simplifies some tasks, but I think the functionality can be duplicated with make. I think the idea is you create a project file that details what is in the project and qmake uses this to build the targets. With make you will define your targets and then decide how to build them.
Yes, but one have to learn make, which can be cumbersome in the beginning. It's really easy with qmake.
I have noticed in qt that they try to do something like autoconf, automake do but much simpler, and I think qmake is a part of that. I wouldn't waste my time on learning it, and just learn the autoconf, automake stuff if you have a substantial enough project to warrant it.
Where did you notice that? It's bogus. Qmake has nothing to do with automake and autoconf whatsoever. Did you ever use it?
No. All I am saying is that it tries to accomplish some of the goals that the autotools tried to accomplish which is cross platform, project based building. No I have not used it mostly because I know make and have not had the need to build across different platforms. I can see how it can be useful in this situation.
Please have a look at http://doc.trolltech.com/3.0/qmake-manual.html
I think Troll's reason for doing it is to make life easier for companies who don't have people with make or system architectural expertise in house, but just want to port their windows applications to Unix.
I've been using qmake a lot, and it's really nice. The above URL would help get you started.
-- Mads Martin Jørgensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort?" -- A. P. J.
Mads Martin Joergensen wrote:
I think the idea is you create a project file that details what is in the project and qmake uses this to build the targets. With make you will define your targets and then decide how to build them.
Yes, but one have to learn make, which can be cumbersome in the beginning. It's really easy with qmake.
I already know make.
Please have a look at http://doc.trolltech.com/3.0/qmake-manual.html
Also on the SuSE 8.0 /usr/share/doc/packages/qt3/...
I've been using qmake a lot, and it's really nice. The above URL would help get you started.
I couldn't find anything that would give me a clue to building a make file with two executable targets. I tried two entries starting: TEMPLATE app, but that didn't work. Also, I couldn't get my own variable $(SRC) defined :-( On the other hand, it does generate nice Makefiles :-) -- Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
participants (3)
-
Jesse Marlin
-
John Lamb
-
Mads Martin Joergensen