This is urgent, because I can't debug in this situation. And this is not qmake, this is programmer who don't know what he did.
There are many problems was introduced with build system after [r1441]. That's why I want to revert it.
Very hard to convey that thought to you.
On Thu, Jan 22, 2015 at 05:55:26PM +0000, PoZitron wrote:
This is urgent, because I can't debug in this situation. And this is not qmake, this is programmer who don't know what he did.
There are many problems was introduced with build system after [r1441]. That's why I want to revert it.
Very hard to convey that thought to you.
Then you need to identify what the problems are, so that we can
resolve these. The only way is forward. The changes you complained
about were to solve other quite significant problems too. You have
often said there are problems, but not said what they are. It is not
helpful to do that.
I fully admit I don't know qmake well. The trouble is, the qmake
documentation is very sparse, so it makes it difficult to figure out
what has to go into qmake to generate the Makefiles we need. It
becomes a reverse engineering problem. If it were just my project, I
would chuck out qmake, and just work with the raw Makefiles, where you
see exactly what needs to be done, rather than use guesswork. But its
not, and some other people seem to like cmake, and so on.
Cheers
Prof Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Professor of Mathematics hpcoder@hpcoders.com.au
University of New South Wales http://www.hpcoders.com.au
Latest project: The Amoeba's Secret
(http://www.hpcoders.com.au/AmoebasSecret.html)
Looks like the following qmake variables will do what we need:
POST_TARGETDEPS
All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.
This list will go after all builtin (and $$PRE_TARGETDEPS) dependencies.
PRE_TARGETDEPS
All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.
This list will go before all builtin dependencies.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is urgent, because I can't debug in this situation. And this is not qmake, this is programmer who don't know what he did.
There are many problems was introduced with build system after [r1441]. That's why I want to revert it.
Very hard to convey that thought to you.
Related
Commit: [r1441]
On Thu, Jan 22, 2015 at 05:55:26PM +0000, PoZitron wrote:
Then you need to identify what the problems are, so that we can
resolve these. The only way is forward. The changes you complained
about were to solve other quite significant problems too. You have
often said there are problems, but not said what they are. It is not
helpful to do that.
I fully admit I don't know qmake well. The trouble is, the qmake
documentation is very sparse, so it makes it difficult to figure out
what has to go into qmake to generate the Makefiles we need. It
becomes a reverse engineering problem. If it were just my project, I
would chuck out qmake, and just work with the raw Makefiles, where you
see exactly what needs to be done, rather than use guesswork. But its
not, and some other people seem to like cmake, and so on.
Cheers
Prof Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Professor of Mathematics hpcoder@hpcoders.com.au
University of New South Wales http://www.hpcoders.com.au
Latest project: The Amoeba's Secret
(http://www.hpcoders.com.au/AmoebasSecret.html)
Related
Commit: [r1441]
Looks like the following qmake variables will do what we need:
POST_TARGETDEPS
All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.
This list will go after all builtin (and $$PRE_TARGETDEPS) dependencies.
PRE_TARGETDEPS
All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.
This list will go before all builtin dependencies.
That worked!