At 11:56 AM 3/17/2006, Christian Ehrlicher wrote:
>Why do these problems raise up once more?
>What's the problem to build & install kdewin32 *before* starting with
>kdelibs4?
>
>We should move kdewin to antoher place asap to not bring up this
>discussion every month... nay ideas? kdesupport?
OK,
>Why do these problems raise up once more?
>What's the problem to build & install kdewin32 *before* starting with
>kdelibs4?
>We should move kdewin to antoher place asap to not bring up this
>discussion every month... nay ideas? kdesupport?
Sorry to beat a dead horse, I didn't realize this was a
Michael Biebl schrieb:
>> Why do these problems raise up once more?
>> What's the problem to build & install kdewin32 *before* starting with
>> kdelibs4?
>
>
> My problem was not to type "make && make install" for kdewin32. I usually
> read the installation instruction and they clearly said so.
Why do these problems raise up once more?What's the problem to build & install kdewin32 *before* starting with
kdelibs4? My problem was not to type "make && make install" for kdewin32. I usually read the installation instruction and they clearly said so.The problem I had was, that FindKDEWin32.cma
On Friday 17 March 2006 17:56, Christian Ehrlicher wrote:
> William A. Hoffman schrieb:
> > At 09:46 AM 3/17/2006, Alex Caudill wrote:
> >> You could:
> >> 1.) use cmakesetup and modify the directories for each library location
> >> 2.) modify the cmake cache by hand
> >>
> >> Is there some reason
William A. Hoffman schrieb:
> At 09:46 AM 3/17/2006, Alex Caudill wrote:
>
>> You could:
>> 1.) use cmakesetup and modify the directories for each library location
>> 2.) modify the cmake cache by hand
>>
>> Is there some reason for treating kdewin32 as a seperate dependency? it
>> seems like you
At 09:46 AM 3/17/2006, Alex Caudill wrote:
>You could:
>1.) use cmakesetup and modify the directories for each library location
>2.) modify the cmake cache by hand
>
>Is there some reason for treating kdewin32 as a seperate dependency? it
>seems like you could add:
>
>IF (WIN32)
> IF (NOT KDEWIN
>After copying the libraries to c:\program files\kdewin32, I get similar
>problems with the other libraries, like libz.lib. They seem to be expected
>in c:\program files\gnuwin32 or something. I have them in
>d:\devel\local\{lib,include}, which are in the default MSVC search paths
>defined by $LIB
> Von: Michael Drüing <[EMAIL PROTECTED]>
> Okay, but then it should not only search in C:\Program Files\kdewin32 but
> also in $KDEDIR/lib, because I don't want my kde installed in c:\program
> files\kdewin32. I have set KDEDIR=d:\kde4 but CMake seems to ignore this.
> Or
> is there any other en
Hi,
> > > I used this batch file to set the correct paths inside a
> VS 2005 command
> > prompt
> > >
> > > @echo off
> > > set OLDPATH=%PATH%
> > > set QTDIR=C:\Programme\qt- win-opensource-src-4.1.1
> > > set CMAKE_DIR=C:\Programme\Develop\CMake
> > > set
> >
> PATH=%OLDPATH%;%QTDIR%\bin;
> Von: Michael Drüing <[EMAIL PROTECTED]>
> > On 3/17/06, Michael Drüing <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > > - cmake -G"NMake Makefiles" ..\kdelibs failed. It couldn't find the
> > > > kdewin32 lib. The problem was, that it looked for a lib called
> > > > kdewin32.lib, while by def
Hi,
> On 3/17/06, Michael Drüing <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > > - cmake -G"NMake Makefiles" ..\kdelibs failed. It couldn't find the
> > > kdewin32 lib. The problem was, that it looked for a lib called
> > > kdewin32.lib, while by default the debug version is built which is
> > > ca
On 3/17/06, Michael Drüing <[EMAIL PROTECTED]> wrote:> Hi,> > > - cmake -G"NMake Makefiles" ..\kdelibs failed. It couldn't find the> > kdewin32 lib. The problem was, that it looked for a lib called
> > kdewin32.lib, while by default the debug version is built which is> > called kdewin32d.lib.> > I
Hi,
> - cmake -G"NMake Makefiles" ..\kdelibs failed. It couldn't find the
> kdewin32 lib. The problem was, that it looked for a lib called
> kdewin32.lib, while by default the debug version is built which is
> called kdewin32d.lib.
I have the same problem. However I built both the "Debug" and
"R
Michael Biebl wrote:
> If I tried to generate the Visual Studio Project files with the latest
> cmake CVS snapshot, the Install Project did not work. It looked for the
> binary cmake in bin/cmake while it was generated in bin/release/cmake.
I just found where/when this bug was introduced. I'll ha
First off, we (Kitware) really need to get a new version of cmake out for kde.
:)
We are working on that.
At 05:08 PM 3/16/2006, Michael Biebl wrote:
>Hi,
>
>I followed the instructions on http://www.kdelibs.com and tried to build
>the lateest qt-4.1.1, cmake and kdelibs.
>My experiences so fa
16 matches
Mail list logo
