2007/12/16, Alexander Neundorf <[EMAIL PROTECTED]>:
> Hi,
>
> attached you can find a small patch which changes the default value of the
> option KDE4_USE_ALWAYS_FULL_RPATH from OFF to ON.
> A better name for that option would be "KDE_BUILD_LIBS_WITH_RPATH", then I
> wouldn't have to explain what i
2008/1/22, Allen Winter <[EMAIL PROTECTED]>:
>
> I suppose we could install a kdepimlibs.h with a version number in it
> and grep for that version.
Why not install a pkg-config file?
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed aw
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 far:
- Building qt-4.1.1 with the supplied patch and msvc2005 was simple.
- Compiling cmake: I downloaded cmake-2.2 and generated NMake Makefiles.
Compiled and i
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
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
Hi all,
when compiling trunk/KDE/kdelibs on windows with cmake/nmake/msvc2005
the build fails with this error message:
<<
Scanning dependencies of target dcopserver
Building CXX object dcop/CMakeFiles/dcopserver.dir/dcopserver.obj
dc
> P.S.:
> Wouldn't it make sense to include the cmake directory (or at least
> parts of it) as external reference? E.g. changes to
> cmake/modules/KDE4Macros.cmake would then be available to all kde
> packages (kdelibs/kdebase/...).
Please forget this comment ;-)
I just noticed that this files are
> knotify/daemon/notifybysound.cpp:71:26: error: akode/player.h: No such file
> or directory
>
> kdesupport mandatory, or check missing?
This was a bug of the libakode2 package in Debian. It contained the
akode-config binary whereas it should be put in the libakode-dev
package. I filed a bug rep
On 3/17/06, William A. Hoffman <[EMAIL PROTECTED]> wrote:
> I have created a new kde CMake release, it can be found here:
>
> http://www.cmake.org/files/v2.3/cmake-2.3.4-20060317-win32.exe
> http://www.cmake.org/files/v2.3/cmake-2.3.4-20060317.tar.gz
>
> You should be able to use the windows binary
Found another problem when using FindKDE3.cmake:
KDE3_LIB_DIR is set to /path/to/kde/lib/libkdecore.so instead of
/path/to/kde/lib.
Linking of course fails if KDE3_LIB_DIR is not one of the standard
paths like /usr/lib.
Michael
___
Kde-buildsystem mailin
This should already work, at least it does for me:
CC=/usr/bin/colorgcc cmake ..
yields
-- Check for working C compiler: /usr/bin/colorgcc
-- Check for working C compiler: /usr/bin/colorgcc -- works
.
.
.
___
Kde-buildsystem mailing list
Kde-buildsystem
Might be a good idea to say why cmake does not use the QTDIR and
KDEDIR variable anymore (because they are deprecated). So
people/developers will hopefully stop using it and not think that
cmake is broken or limited.
Michael
___
Kde-buildsystem mailing
On 3/22/06, Thiago Macieira <[EMAIL PROTECTED]> wrote:
> William A. Hoffman wrote:
> >The current FindQT4.cmake in kde looks for qmake-qt4, then qmake.
> >Is qmake-qt4 standard? When I build and install qt-copy, I only
> >get a qmake, however there is a qmake-qt4 on the machine that gets
> >found,
I would simply go with qmake and don't care for qmake-qt4, as it is
Debian specific.
If people don't specify Qt4 as default (i.e. create the qmake and
other symlinks) because they want to keep Qt3 around, they could still
use -DQT_QMAKE_EXECUTABLE=qmake-qt4
Just my 2¢
On 3/22/06, David Faure <[EM
cmake/modules/CMakeLists.txt in kdelibs4_snapshot still references
kde3init_dummy.cpp.in which makes "make install" fail. It would be a
good idea imo to merge back the changes from trunk where this seems to
be fixed already.
Michael
___
Kde-buildsystem m
On 3/24/06, Allen Winter <[EMAIL PROTECTED]> wrote:
> Hi CMake Devs,
>
> Perhaps this should go direct to your project mailing list, but since I know
> you are here
>
> There has been quite a number of folks asking for the colorful output that
> unsermake used to have.
> The colors were much,
Compiling kdebase against kdelibs4_snapshot failed at four places for
me because of missing headers. (Xcursor/Xrender headers were not
found).
I added X11_Xcursor_INCLUDE_PATH/X11_Xrender_INCLUDE_PATH to the
include path for the failing targets to fix this. Please find the
attached patch.
Cheers,
Does cmake have support for installing man pages, something like
man_MANS for automake?
The macro should be clever enough to figure out by the filename, e.g.
foo.1, where to put it, so that I don't have to rename it myself.
gzipping would be a bonus.
Cheers,
Michael
___
On 3/31/06, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> On Friday 31 March 2006 00:04, Michael Biebl wrote:
> > Does cmake have support for installing man pages, something like
> > man_MANS for automake?
>
> What does this exactly do ?
http://www.gnu.org/software/au
I currently get the following build errors under Windows XP using msvc
2005/cmake 2.4.1/nmake:
1.)
Linking CXX shared module ..\..\bin\keramik.dll
Creating library ..\..\bin\keramik.lib and object ..\..\bin\keramik.exp
keramik.obj : error LNK2019: unresolved external symbol "__declspec(dllimpor
Looking at the FindKDE module (cmake 2.4.1), exceptions are disabled
unconditionally.
I noticed that because I wanted to build an application which uses exceptions.
The old autotools build system tried to determine if execptions are
supported during configure time, at least I found these test in
ac
2006/6/23, Simon Perreault <[EMAIL PROTECTED]>:
> Hi,
>
> Currently, FindQt4.cmake searches for "qmake" before "qmake-qt4". I think
> that's wrong and that it should be reversed.
>
> Why: When qmake (from Qt3) and qmake-qt4 are in the $PATH, the check fails
> unless the order is reversed.
>
> Why n
Recently the build system of kdesvn [1], a KDE3 application, was
switched from auto* to cmake.
Unfortunately the build fails for me (running a Debian unstable box
with latest KDE and qt3).
The build fails on compilation of logmessage.cpp, which is a
autogenerated file by uic using logmessage.ui. T
2006/8/31, Andreas Pakulat <[EMAIL PROTECTED]>:
> On 31.08.06 00:09:48, Michael Biebl wrote:
> > Recently the build system of kdesvn [1], a KDE3 application, was
> > switched from auto* to cmake.
>
> Well, the autotools stuff is still there ;)
Yes, but i
2006/8/31, Thomas Baumgart <[EMAIL PROTECTED]>:
> On Thursday 31 August 2006 00:09, Michael Biebl wrote:
>
> [...]
>
> > It seems, that the autogenerated *.cpp file is missing a ktextedit.h
> > include. After investigating the problem, I found that aut
2006/8/31, Dirk Mueller <[EMAIL PROTECTED]>:
> On Thursday 31 August 2006 00:09, Michael Biebl wrote:
>
> > Recently the build system of kdesvn [1], a KDE3 application, was
> > switched from auto* to cmake.
> > Unfortunately the build fails for me (running a Debian un
26 matches
Mail list logo
