On Sunday 18 April 2010 09:50:42 ext Andre Poenitz wrote:
> On Sun, Apr 18, 2010 at 10:58:34AM +1000, Brad Hubbard wrote:
> > Not sure how comprehensive fakevim emulation is supposed to be but
> > when attempting yank inner word "yiw" the fakevim plugin interprets
> > the i as the input mode comman
Coda/nobodyhere:
According to my experience (however little), it works well as long as we
do it the way Adam suggested. As long as we put all relevant system
dependent information in the .pro file, then qmake will generate an
actual makefile tailored for each particular platform that reflects
what
The makefile is generated directly from the .pro file. This is where
everything needs to go, especially if you want your project to work if
you're building it at the command line instead of from within Creator.
The .pro.user file is really just intended for short-term,
system-specific, non-general
This makes Qt Creator sound broken? I mean, what's the point of having it
generate your make files for you (in the .pro.user file), if you have to then
rewrite them manually anyway (in the .pro file)?
regards
- Original Message -
From: "Coda Highland"
To: qt-creator@trolltech.com
Sent
No, we mean the .pro file. qmake's file format supports a lot of logic
there, including platform detection (scopes like win32, unix, and
macx). Never edit the .pro.user file and avoid using Creator's
built-in tools for changing the build settings -- do all the work
directly in the .pro file except
Below is some info I found when I started googling for (qt creator .pro
.pro.user), instead of just (qt creator build settings)
So definitely plenty of other people are running into this too...
...
>From
>http://qtcreator.blogspot.com/2009/10/project-not-linked-when-dependent.html#comments
> :
You mean edit and (svn commit) the project's ".pro.user" file? (Not the
project's ".pro" file?)
And the .pro file has hardcoded / absolute paths in it, so how does this let me
do a simple (svn checkout and build that just works, with the exact same
.pro.user file) for (multiple computers) and
Fellows:
Today while trying to compile QtCreator 2.0.0-beta "make" kept quitting
with the following error message:
../../../../qtcreatorgit/src/plugins/help/centralwidget.cpp:44:37:
error: /usr/local/Trolltech/Qt-4.7.0/include/QtGui/QPrintPreviewDialog:
Permission denied
I check the source file
Hi,
I mostly finished a Qt application that I now want to run and debug on
my N900.
I pulled and built qt-creator master branch and installed the latest
MADDE 0.6.14. First I tried a minimal application: I created a new
project "hello-world" using the Mobile Qt Application wizard. I didn't
change
Set you build settings, project directories and platform-specific configs in
the .pro file.
On 18 Apr 2010, at 09:26, nobodyhere wrote:
> Is there information on how to (svn commit) cross platform (Windows, Mac,
> Linux) build settings for a Qt Creator project, that doesn't have any
> absolute
Is there information on how to (svn commit) cross platform (Windows, Mac,
Linux) build settings for a Qt Creator project, that doesn't have any absolute
paths?
I created a new project on Windows, then (svn commit) it. Then I did (svn
checkout) of the project on Mac OS. Unfortunately, I had to
On Sun, Apr 18, 2010 at 10:58:34AM +1000, Brad Hubbard wrote:
> Not sure how comprehensive fakevim emulation is supposed to be but
> when attempting yank inner word "yiw" the fakevim plugin interprets
> the i as the input mode command. this also effects commands like "viw"
> and "viwp" which can be
12 matches
Mail list logo
