Hi,
Hamid wrote:
> But in this specific case, i.e. kdevelop, I still have problem.
> I have installed all the necessary packages for Qt (binary and headers)
> using debian packages and I use a lot of "--with-qt-" to pass the right
> directories to the script and it still does not feel like helpi
Thank you all for the responses.
As you said, I could solve some of the problems by installing the
relative "-dev" package.
But in this specific case, i.e. kdevelop, I still have problem.
I have installed all the necessary packages for Qt (binary and headers)
using debian packages and I use a lot
On Fri, May 30, 2003 at 10:10:10PM -0500, Kirk Strauser wrote:
> Also, you have to realize that half (I'm being charitable) of the developers
> you'll be downloading from have a lot of hard-coded paths in their configure
> scripts. Get used to specifying lots of "--with-foo=/usr/include/foo"
> opt
On Fri, May 30, 2003 at 09:59:21PM -0400, Hamid wrote:
> I am using Debian for a month now and I used to have RedHat 8.0 In
> RedHat, I could download a tar ball of a project (say, KDevelop
> snapshots) and use provided ./configure script to compile the
> application and use it.
>
> But in Debian,
Hi
I am using Debian for a month now and I used to have RedHat 8.0
In RedHat, I could download a tar ball of a project (say, KDevelop
snapshots) and use provided ./configure script to compile the
application and use it.
But in Debian, I am having hard times with this type of approach. For
exampl
5 matches
Mail list logo