From: "Marco Costalba" <mcostalba@gmail.com>
To: "Rob Arnold" <rob@loci.net>
Cc: info@trolltech.com, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Qt/mac, 10.5, qgit
Date: Thu, 30 Aug 2007 13:54:10 +0200 [thread overview]
Message-ID: <e5bfff550708300454m438d876ck7de6d1e9508d96af@mail.gmail.com> (raw)
In-Reply-To: <65E7CC32-8B78-4037-9BC2-9129D79F377E@loci.net>
On 8/30/07, Rob Arnold <rob@loci.net> wrote:
> Wasn't sure where to send this to. I'm writing to report an issue you
> may want to take a look at, if you don't already know about it.
>
Thanks for your report. Normally would be more convenient to send the
qgit related issues to git mailing list where there are a number of
experienced users.
Unfortunately I don't have a mac so I cannot reproduce the bug.
If would be great if someone on the list with experience on
installation of qgit on a mac could give us some hints.
Thanks
Marco
Following the original e-mail:
Wasn't sure where to send this to. I'm writing to report an issue you
may want to take a look at, if you don't already know about it.
I'm far from an expert Qt person, but am a developer and do use git
for revision control on a daily basis. I thought I'd give compiling
qgit on a seed version of 10.5 a shot, since I liked the idea of a
nicer looking, native interface for a viewer.
I had some issues that looked like they were based on interaction
between qmake and the new xcode 3. Thought you guys should know, just
in case you somehow don't already.
QGit can be found at: http://digilander.libero.it/mcostalba/
I was using the Qt 4 version, cloned from: git://git.kernel.org/pub/
scm/qgit/qgit4.git
The installation procedure in the README doesn't work as written for a
mac. Qmake doesn't seem to make an xcode project that does anything
useful if you run it in the base project directory, unless you use --
recursive as an option. However, if you run it from the src
directory, or use --recursive, you do get a seemingly ok
qgit.xcodeproj project. I don't know if there's a way to generate
Makefiles instead, but my problem lies in the Xcode project. The
problem comes when you try to build it from XCode. You get 5 errors
during checking dependencies:
Build setting $(TARGET_BUILD_DIR) undefined
Build setting $(BUILT_PRODUCTS_DIR) undefined
Build setting $(TARGET_TEMP_DIR) undefined
Build setting $(TEMP_DIR) undefined
Build setting $(DERIVED_FILE_DIR) undefined
Not sure why these standard vars are undefined - maybe it's a change
is the way XCode 3 works, but I don't get those errors opening other
projects, and I don't see where those references are in any of the Qt
generated files, so really not sure what's going on with it, or how to
fix it.
I did install the full Qt 4.3.1 .dmg file rather than building Qt
itself from source; not sure if that could be an issue.
In any event, thought I'd let you guys know, not to try to get help or
anyone to fix anything, but just to give you the information, in case
you didn't have it and might find it useful.
Thanks, and I'll continue to use Qt and qgit where I can :)
parent reply other threads:[~2007-08-30 11:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <65E7CC32-8B78-4037-9BC2-9129D79F377E@loci.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5bfff550708300454m438d876ck7de6d1e9508d96af@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=info@trolltech.com \
--cc=rob@loci.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).