OK, apparently none of you guys actually understood my initial question. I'm
trying to construct an external Makefile project. I'd be perfectly happy
with hacking around in a .pro file if that was actually an option, but it
isn't. Am I just stuck? All I really need is for Qt Creator to explicitly
support an empty builddir spec in the .creator.user format, and make the
abs-pathing internal and temporary (not saved back to the file). That single
fix will make me a very happy user.

On Fri, Mar 12, 2010 at 7:30 AM, Robert Caldecott <
[email protected]> wrote:

> So in other words, I'd you don't like it, go take a running jump.
> Unbelievable. You have just lost an avid supporter. Congratulations.
>
> On 12 Mar 2010, at 15:20, Oswald Buddenhagen <[email protected]
>  > wrote:
>
> > On Fri, Mar 12, 2010 at 01:36:45PM +0100, ext Robert Caldecott wrote:
> >> Your comment was beyond harsh - it was rude IMHO.
> >>
> > yes. deservedly so. not for this mail of danny, but for his "life
> > work".
> > there's a limit to what we are willing (and can be expected) to take.
> >
> >> This is not an unreasonable request. I shouldn't have to expect my
> >> team to hand-craft .pro files in this way.
> >>
> > danimo explained what the reasons are and what you can do to improve
> > it.
> > the eclipsers want to attack that problem as well. feel free to find
> > inspiration there. ;)
> > _______________________________________________
> > Qt-creator mailing list
> > [email protected]
> > http://lists.trolltech.com/mailman/listinfo/qt-creator
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>



-- 
Bryce Schober
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to