All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Filippo Zangheri <filippo.zangheri@yahoo.it>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] qgit-2.1 and qgit-1.5.8
Date: Tue, 01 Jan 2008 09:55:44 +0200	[thread overview]
Message-ID: <4779F200.1020507@panasas.com> (raw)
In-Reply-To: <e5bfff550712311007j1cd8223es51b6a59dfb958193@mail.gmail.com>

On Mon, Dec 31 2007 at 20:07 +0200, "Marco Costalba" <mcostalba@gmail.com> wrote:
> On Dec 31, 2007 6:47 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
>> On Mon, Dec 31 2007 at 13:58 +0200, "Marco Costalba" <mcostalba@gmail.com> wrote:
>>> On Dec 31, 2007 11:59 AM, Filippo Zangheri <filippo.zangheri@yahoo.it> wrote:
>>>> Hi,
>>>>
>>>> I git-cloned qgit-2.1 from your repository, then ran `qmake qgit.pro`, but `make` gave me errors.
>>> Yes, you need qmake of Qt4 not the Qt3 one.
>>>
>> <snip>
>>
>> A Theoretical question.
>> Is it possible to compile Qt4 app all statically linked and run it on a Qt3 based KDE
>> machine. Some thing like the windows installation, where every thing is self-contained?
>>
> 
> It's also very practical...I have _only_ KDE 3 installed, not KDE 4 ;-)
> 
> I have both Qt4 and Qt3 development (shared) libraries installed and
> there is absolutely no compatibility problem, the only thing you have
> to remember is when running
> 
> qmake qgit.pro
> 
> the first time, you need to be sure is the Qt4 qmake, not the Qt3.
> Because I have Qt3 qmake in path, not the Qt4 one, I need to
> explicitly give the whole path the first time I configure the sources,
> something like
> 
> /usr/lib/qt4/bin/qmake qgit.pro
> 
> Then no other settings are needed, when you call make, the Makefiles
> are already built by qmake to search for the correct libraries.
> 
> 
> Hope this helps...
> 
> Marco

Thanks because of your help I was brave enough to install qt4 and compile qgit.
It works.

We use it a lot here. When the guys make a mess, and you need to figure what
happened than qgit is your only friend. I intend to hack some extra stuff that
we need often.

Boaz

  reply	other threads:[~2008-01-01  7:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31  7:35 [ANNOUNCE] qgit-2.1 and qgit-1.5.8 Marco Costalba
2007-12-31  7:35 ` Marco Costalba
2007-12-31 10:59 ` Filippo Zangheri
2007-12-31 11:58   ` Marco Costalba
2007-12-31 17:47     ` Boaz Harrosh
2007-12-31 18:07       ` Marco Costalba
2008-01-01  7:55         ` Boaz Harrosh [this message]
2008-01-01  8:26           ` Marco Costalba

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=4779F200.1020507@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=filippo.zangheri@yahoo.it \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcostalba@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.