On Wednesday 27 May 2015 11:19:08 Boudewijn Rempt wrote:
On Wed, 27 May 2015, Matthias Kretz wrote:
I have to admit I didn't know about this change in cmake. I think it's the
right direction, though. I just started to read the relevant cmake
documentation and then I'll see whether I can
Ninja dosen't generate that quoted include line, for the short term, how
about stop supporting GNU Make, tell distro maintainers to generate ninja
target when running Cmake?
On May 23, 2015 5:06 AM, Aleix Pol aleix...@kde.org wrote:
On Sat, May 23, 2015 at 11:51 AM, Boudewijn Rempt
Hi,
On Monday 25 May 2015 11:50:35 Alex Merry wrote:
The issue here is that Vc's macros implicitly assume that all compilation
flags (including include paths) are done at the directory level (with
include_directories() and setting CMAKE_CXX_FLAGS etc), while CMake is
moving towards doing
I'm not sure if I understood the issue. If we need to pass the -I
parameters to vc_compile_for_all_implementations, then something like
https://git.reviewboard.kde.org/r/115110/diff/1/ might work.
Em 23/05/2015 09:07, Aleix Pol aleix...@kde.org escreveu:
On Sat, May 23, 2015 at 11:51 AM,
On Wed, 27 May 2015, Matthias Kretz wrote:
Hi,
On Monday 25 May 2015 11:50:35 Alex Merry wrote:
The issue here is that Vc's macros implicitly assume that all compilation
flags (including include paths) are done at the directory level (with
include_directories() and setting CMAKE_CXX_FLAGS
On Mon, 25 May 2015, Alex Merry wrote:
The issue here is that Vc's macros implicitly assume that all compilation
flags (including include paths) are done at the directory level (with
include_directories() and setting CMAKE_CXX_FLAGS etc), while CMake is moving
towards doing things at the target
On Saturday 23 May 2015 11:51:55 Boudewijn Rempt wrote:
Sorry for the extensive cross-posting in advance, please when replying, do
a reply-all.
Just so everyone is on the same page: Vc is a template library that makes
it easy to build vectorized code using a single source file. Krita uses Vc
to extract include directories etc, but
I'm not sure if generator expressions are powerful enough to deal with
the compile flags properly.
Hm, that doesn't sound too hopeful :-(.
Well, it should work for the include directories just fine, which seems to be
the problem you're actually
On Mon, 25 May 2015, Alex Merry wrote:
include_directories($JOIN:${KDE4_INCLUDES}, -I)
Well, I've tried that before, I think... It expands to this:
/usr/bin/c++ -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
On Mon, 25 May 2015, Alex Merry wrote:
Ah, yes. You may get somewhere with
include_directories($JOIN:${KDE4_INCLUDES}, -I)
Basically, this should replace all those semicolons in the generated output
with -I, which should produce a correct command line. This is untested,
though.
Hm... No
On Monday 25 May 2015 13:50:08 Boudewijn Rempt wrote:
On Mon, 25 May 2015, Alex Merry wrote:
Ah, yes. You may get somewhere with
include_directories($JOIN:${KDE4_INCLUDES}, -I)
Basically, this should replace all those semicolons in the generated
output
with -I, which should produce
. After that, running cmake and make VERBOSE=1 will give the
exact problem I've got.
Boudewijn
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
On Monday 25 May 2015 15:31:52 Boudewijn Rempt wrote:
http://www.valdyas.org/~boud/vc-cmake-3.tgz is as minimal as I know how to
make it: you still need qt, KDELibs4Support and extra-cmake-modules
installed. After that, running cmake and make VERBOSE=1 will give the
exact problem I've got.
I
Hm, to expand on that: if you're running into compile problems, well, then
my problem would be solved. I've tested on kubuntu vivid, with cmake 3.0.2
and the 5.9.0 packages.
On Mon, 25 May 2015, Boudewijn Rempt wrote:
Weird, it worked for me:
https://paste.kde.org/pmvwwhyqp -- in fact
how to
make it: you still need qt, KDELibs4Support and extra-cmake-modules
installed. After that, running cmake and make VERBOSE=1 will give the
exact problem I've got.
I get compiler issues with that, but the problems I'm getting are because
KoOptimizedCompositeOpFactoryPerArch.cpp doesn't
://www.valdyas.org/~boud/vc-cmake-3.tgz is as minimal as
I know how to
make it: you still need qt, KDELibs4Support and
extra-cmake-modules
installed. After that, running cmake and make VERBOSE=1 will
give the
exact problem I've got.
I get
On Mon, 25 May 2015, Stephen Kelly wrote:
Boudewijn Rempt wrote:
Here's an SSCCE that demonstrates the problem with Vc 0.7.4:
cmake_minimum_required(VERSION 3.0)
project(VcTest)
set(CMAKE_INCLUDE_CURRENT_DIR ON)
find_package(Qt5Core REQUIRED)
find_package(Vc REQUIRED)
# Uncomment
Sorry for the extensive cross-posting in advance, please when replying, do
a reply-all.
Just so everyone is on the same page: Vc is a template library that makes
it easy to build vectorized code using a single source file. Krita uses Vc
to optimize blending colors, creating masks and much
On Sat, May 23, 2015 at 11:51 AM, Boudewijn Rempt b...@valdyas.org wrote:
Sorry for the extensive cross-posting in advance, please when replying, do a
reply-all.
Just so everyone is on the same page: Vc is a template library that makes it
easy to build vectorized code using a single source
Well, _I_ and using make and nmake... So that's not a solution either. It
really just needs to be fixed properly!
On Sat, 23 May 2015, Yue Liu wrote:
Ninja dosen't generate that quoted include line, for the short term, how about
stop supporting GNU Make, tell
distro maintainers to generate
On Sat, 23 May 2015, Andrius da Costa Ribas wrote:
I'm not sure if I understood the issue. If we need to pass the -I parameters to
vc_compile_for_all_implementations, then
something like https://git.reviewboard.kde.org/r/115110/diff/1/ might work.
Well, it's not that, it's also not
On Friday 28 October 2011, Sebastian Trüg wrote:
Michael,
would you mind taking care of this without raising the min cmake to
2.8.3, please?
Sebastian, have you been able to fix this issue already ?
Alex
___
Kde-buildsystem mailing list
Soprano 2.7.3 has been released today. :)
On 10/31/2011 09:12 PM, Alexander Neundorf wrote:
On Friday 28 October 2011, Sebastian Trüg wrote:
Michael,
would you mind taking care of this without raising the min cmake to
2.8.3, please?
Sebastian, have you been able to fix this issue already
On Monday 31 October 2011, Sebastian Trüg wrote:
Soprano 2.7.3 has been released today. :)
Does that mean yes ?
Alex
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
On 10/31/2011 10:12 PM, Alexander Neundorf wrote:
On Monday 31 October 2011, Sebastian Trüg wrote:
Soprano 2.7.3 has been released today. :)
Does that mean yes ?
:D
it does indeed.
Alex
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
Sorry i am only able to read emails these days. I made the wrong decision to
switch internet providers which led to me beeing without an landline internet
connection for about 1,5 month now.
Hope to be back online in the next days. Hope!
So if there is need for a fix it has either to wait or
Michael,
would you mind taking care of this without raising the min cmake to
2.8.3, please?
Cheers,
Sebastian
On 10/27/2011 10:14 PM, Alexander Neundorf wrote:
On Thursday 27 October 2011, kaushik wrote:
Hi,
2011/10/28 Alexander Neundorf neund...@kde.org
On Thursday 27 October 2011,
Hi,
I am trying to build soprano from git, but it is not getting built properly.
I have both libraptor1 and libraptor2 installed.
I have devel packages of libraptor1 not installed and devel packages of
libraptor2 installed.
Distro is debian.
The output of cmake is
-- Found Qt-Version 4.7.4
--
On Thursday 27 October 2011, kaushik wrote:
Hi,
I am trying to build soprano from git, but it is not getting built
properly. I have both libraptor1 and libraptor2 installed.
I have devel packages of libraptor1 not installed and devel packages of
libraptor2 installed.
Distro is debian.
The
Hi,
2011/10/28 Alexander Neundorf neund...@kde.org
On Thursday 27 October 2011, kaushik wrote:
Hi,
I am trying to build soprano from git, but it is not getting built
properly. I have both libraptor1 and libraptor2 installed.
I have devel packages of libraptor1 not installed and devel
On Thursday 27 October 2011, kaushik wrote:
Hi,
2011/10/28 Alexander Neundorf neund...@kde.org
On Thursday 27 October 2011, kaushik wrote:
Hi,
I am trying to build soprano from git, but it is not getting built
properly. I have both libraptor1 and libraptor2 installed.
I have
digits would be enough?
Is it the regular expression which fails or the comparison of the numbers ?
It looks like the comparison is the problem:
MATH(EXPR ${_normalized_version} ${_major_vers}*1 + ${_minor_vers}*100 +
${_patch_vers})
Can you try whether it works if you use if( VERSION_LESS
Howdy,
In kde-workspace/solid/CMakeLists.txt we have this:
macro_ensure_version_range(0.7.0 ${NETWORKMANAGER_VERSION} 0.8.10 NM_0_7)
which is failing for me because in Fedora15, NETWORKMANGER_VERSION=0.8.9997
So this is a request for someone to look at fixing macro_ensure_version_range()
to
On Monday 18 April 2011 19:44:38 Danny M.M.W wrote:
I try to find how to configure my Microsoft Visual C++ 2010 Express edition
with KDE or even I try to find where all the header files are on what I
just installed. I am not a C++
professional but I know enough, and I seem to not be able to
I try to find how to configure my Microsoft Visual C++ 2010 Express edition
with KDE or even I try to find where all the header files are on what I just
installed. I am not a C++
professional but I know enough, and I seem to not be able to find any
instructions.
On Monday 18 April 2011, Danny M.M.W wrote:
I try to find how to configure my Microsoft Visual C++ 2010 Express
edition with KDE or even I try to find where all the header files
are on what I just installed. I am not a C++
professional but I know enough, and I seem to not be able to find any
;a=blob;f=Source/cmTarget.cxx;h=45ba3584
;hb=v2.8.2#l4207
Note the TODO comment. It does not recognize shared libraries
by file name. This causes your problem because the file
/path/to/kde4/trunk/support/libphoton.so
does not end up in the list of known dependent libraries.
Therefore
when khtml was built
- CMake did not recognize it as a runtime dependency of khtml
due to the lack of implementation at the above-mentioned TODO
Hmm, wouldn't we still have a problem ?
Qt has been built with phonon, and some parts of Qt most probably link
against
this phonon in qt/lib
Greetings,
google-gadgets-for-linux which is a prerequisite for compiling KDE4.x does
not compile with the current standard versions of xulrunner (
http://code.google.com/p/google-gadgets-for-linux/issues/detail?id=352 ).
I have tried version 11.2 and the current version in svn on a few
Em Domingo 27. Junho 2010, às 14.30.45, lI escreveu:
I was wondering if there is an alternative to using this program or a
fix from somewhere within kde.
Remove the package. It's not a mandatory dependency of KDE.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior
On Sunday 24 January 2010 20:44:12 Alexander Neundorf wrote:
On Sunday 24 January 2010, Dario Freddi wrote:
On Sunday 24 January 2010 18:58:01 you wrote:
...
Ah, ok.
set(FOO bar ... CACHE) behaves as follows:
If FOO is not in the cache, it is written in the cache with the
Sorry for the delay. Here goes.
On Saturday 16 January 2010 19:27:19 Alexander Neundorf wrote:
On Thursday 14 January 2010, Dario Freddi wrote:
On Wednesday 13 January 2010 20:21:50 Alexander Neundorf wrote:
...
[...]
How KDE4_AUTH_POLICY_FILES_INSTALL_DIR is not ok.
The
checks if the chosen backend is actually available
3 - If not, the build system falls back to another one.
I thought that could have fixed this problem, is it just enough to put the
cached variable at the end?
Ah, ok.
set(FOO bar ... CACHE) behaves as follows:
If FOO is not in the cache
On Sunday 24 January 2010, Dario Freddi wrote:
On Sunday 24 January 2010 18:58:01 you wrote:
...
Ah, ok.
set(FOO bar ... CACHE) behaves as follows:
If FOO is not in the cache, it is written in the cache with the value
bar (this happens during the first call in the first run).
If
On Saturday 23 January 2010, Dario Freddi wrote:
Sorry for the delay. Here goes.
--- kdecore/auth/ConfigureChecks.cmake (revisione 1079059)
+++ kdecore/auth/ConfigureChecks.cmake (copia locale)
@@ -1,8 +1,11 @@
### checks for kdecore/kauth ###
-set(KAUTH_BACKEND CACHE
On Thursday 14 January 2010, Dario Freddi wrote:
On Wednesday 13 January 2010 20:21:50 Alexander Neundorf wrote:
...
[...]
How KDE4_AUTH_POLICY_FILES_INSTALL_DIR is not ok.
The information coming from the KDELibsDependencies.cmake file, i.e.
written by
On Wednesday 13 January 2010 20:21:50 Alexander Neundorf wrote:
[...]
It's a good idea to put this into the cache, but please put it in the cache
without ${CMAKE_INSTALL_PREFIX}. If you do it as it is now, later changes
to CMAKE_INSTALL_PREFIX in the cache will have no effect on
On Tuesday 12 January 2010, Alexander Neundorf wrote:
...
I'll have a closer look at this tomorrow.
Ok, here we go.
Index: cmake/modules/FindPolkitQt-1.cmake
===
--- cmake/modules/FindPolkitQt-1.cmake(revisione 1072643)
/FindKDE4Internal.cmake.
Does this do what you want ?
Unfortunately not. The problem here is that we really want to store some
data: KAuth is backend based, and we have no knowledge at build time
(outside KDELibs) of which backend was built, hence how to handle it.
This is probably a reason
.
Look for the macro _SET_FANCY() in
kdelibs/cmake/modules/FindKDE4Internal.cmake.
Does this do what you want ?
Unfortunately not. The problem here is that we really want to store
some data: KAuth is backend based, and we have no knowledge at build
time (outside KDELibs
prefix, then we reuse the variable (e.g.
KDE4_AUTH_POLICY_FILES_INSTALL_DIR) from kdelibs.
Look for the macro _SET_FANCY() in
kdelibs/cmake/modules/FindKDE4Internal.cmake.
Does this do what you want ?
Unfortunately not. The problem here is that we really want to store some data:
KAuth
CMAKE_INSTALL_PREFIX is the same as
the kdelibs install prefix, then we reuse the variable (e.g.
KDE4_AUTH_POLICY_FILES_INSTALL_DIR) from kdelibs.
Look for the macro _SET_FANCY() in
kdelibs/cmake/modules/FindKDE4Internal.cmake.
Does this do what you want ?
Unfortunately not. The problem
On Monday 14 December 2009, Dario Freddi wrote:
Hello Alex and guys,
as you might remember, we're not installing FindPolkitQt.cmake anymore.
Unfortunately, I found out that this creates a small problem, in
KDE4Macros, here:
if (NOT POLKITQT_FOUND)
macro_optional_find_package
Hi, I'm a developer of KVIrc, a project that uses kde as an optional
component.
A fedora packager reported us a problem compiling kvirc with cmake 2.8
(https://svn.kvirc.de/kvirc/ticket/655); after a lot of investigation,
we found out that the problem was cmake being fooled in using both kde's
On Monday 21 December 2009, ctrlaltca wrote:
Hi, I'm a developer of KVIrc, a project that uses kde as an optional
component.
A fedora packager reported us a problem compiling kvirc with cmake 2.8
(https://svn.kvirc.de/kvirc/ticket/655); after a lot of investigation,
we found out
Hello Alex and guys,
as you might remember, we're not installing FindPolkitQt.cmake anymore.
Unfortunately, I found out that this creates a small problem, in KDE4Macros,
here:
if (NOT POLKITQT_FOUND)
macro_optional_find_package(PolkitQt)
endif (NOT POLKITQT_FOUND
On Tuesday 03 November 2009, Volker Krause wrote:
On Thursday 29 October 2009 19:49:09 Alexander Neundorf wrote:
On Thursday 29 October 2009, Volker Krause wrote:
On Wednesday 28 October 2009 18:55:06 Alexander Neundorf wrote:
...
As Michael already asked, can you give a bit more
On Thursday 29 October 2009 19:49:09 Alexander Neundorf wrote:
On Thursday 29 October 2009, Volker Krause wrote:
On Wednesday 28 October 2009 18:55:06 Alexander Neundorf wrote:
...
As Michael already asked, can you give a bit more detail on this ?
What I can imagine in issues is
*
On Wednesday 28 October 2009 18:55:06 Alexander Neundorf wrote:
On Wednesday 28 October 2009, Volker Krause wrote:
On Tuesday 27 October 2009 16:42:26 Michael Jansen wrote:
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime
On Thursday 29 October 2009, Volker Krause wrote:
On Wednesday 28 October 2009 18:55:06 Alexander Neundorf wrote:
...
As Michael already asked, can you give a bit more detail on this ?
What I can imagine in issues is
* updating required packages, e.g. Qt
* stuff hangs while executing the
From my experience with maintaining the automatic builds on
dashboard.akonadi-project.org, the problem is the considerable time needed
to maintain those automatic builds. I have to intervene manually more or
less every other day because something broke/hangs/flooded the
disk/whatever.
I
On Tuesday 27 October 2009 18:05:33 Christophe Giboudeaux wrote:
When fixing that problem locally i encountered two other problems.
First a kdepim developer objecting to my change because Nepomuk already
is optional in his opinion. I think we have a problem with people
understanding
On Wednesday 28 October 2009, Volker Krause wrote:
On Tuesday 27 October 2009 16:42:26 Michael Jansen wrote:
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime. Specifying
-DWITH_Nepomuk=0 worked (I have nepomuk compiled
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime. Specifying -DWITH_Nepomuk=0
worked (I have nepomuk compiled. onto2vocab... just crashes on execution).
It is only on the first glimpse an optional dependence in kdepim. Therefore
Hi,
On Tuesday 27 October 2009 16:42:26 Michael Jansen wrote:
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime. Specifying -DWITH_Nepomuk=0
worked (I have nepomuk compiled. onto2vocab... just crashes on execution).
It is only
On Tuesday 27 October 2009, Michael Jansen wrote:
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime. Specifying -DWITH_Nepomuk=0
worked (I have nepomuk compiled. onto2vocab... just crashes on execution).
It is only on the first
On Tuesday 27 October 2009 16:42:26 Michael Jansen wrote:
Hi
Because of some qt problem i had to deactivate Nepomuk.
It is a optional dependency in kdebase/runtime. Specifying -DWITH_Nepomuk=0
worked (I have nepomuk compiled. onto2vocab... just crashes on execution).
It is only
Hi all,
My problem is that I use kde-qt which indicates to build Qt Phonon which I
did. I don't install Qt.
I cannot build kdebase because the FindPhonon.cmake fails to retrieve phonon
version.
Mainly, this line fails
set(_phonon_namespace_header_file
${PHONON_INCLUDE_DIR}/phonon
2009/7/3 Anne-Marie Mahfouf annemarie.mahf...@free.fr:
Hi all,
My problem is that I use kde-qt which indicates to build Qt Phonon which I
did. I don't install Qt.
Isn't Qt always supposed to be installed in a different directory?
I cannot build kdebase because the FindPhonon.cmake fails
Le vendredi juillet 3 2009 8:54:15 PM, Raphael Kubo da Costa a écrit :
2009/7/3 Anne-Marie Mahfouf annemarie.mahf...@free.fr:
Hi all,
My problem is that I use kde-qt which indicates to build Qt Phonon which
I did. I don't install Qt.
Isn't Qt always supposed to be installed
Raphael Kubo da Costa wrote:
2009/7/2 annemarie.mahf...@free.fr:
hi,
Since the change to kde-qt, the recommanded configuration for Qt is to
build with Phonon. Following a mail to kde-devel mailing list about
Phonon I tried this morning a clean build (with no installed Phonon
from
2009/7/2 Thiago Macieira thi...@kde.org:
Raphael Kubo da Costa wrote:
2009/7/2 annemarie.mahf...@free.fr:
hi,
Since the change to kde-qt, the recommanded configuration for Qt is to
build with Phonon. Following a mail to kde-devel mailing list about
Phonon I tried this morning a clean build
Excerpts from Raphael Kubo da Costa's message of Thu Jul 02 21:08:22 +0200 2009:
Now I think the only question left is which version is preferred. And
if it's kde-qt's, I'd also like to know if there are plans to remove
phonon from kdesupport.
Not removed, but it could be reduced to just the
)
target_link_libraries(kjs_bin ${KJSLIBNAME})
In this case the manifest will be added to the executable named
kjs_bin.exe, which is wrong.
A solution for this problem would be to call KDE4_ADD_MANIFEST after
set_target_properties and not in kde4_add_executable, say in a kde
specific
On Friday 30 January 2009, Hasso Tepper wrote:
Hasso Tepper wrote:
And FindPulseAudio.cmake is not the only one, seems. At least
FindIDN.cmake in kdenetwork breaks the same way here.
I rewrote the FindIDN.cmake getting inspiration from other cmake files
using pkg-config. The result is
Linking CXX shared module ../../../lib/kded_phononserver.so
cd /home/kde-devel/kde/build/KDE/kdebase/runtime/phonon/kded-module
/usr/pkg/bin/cmake -E cmake_link_script
CMakeFiles/kded_phononserver.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -Woverloaded-virtual -fvisibility=hidden -O2 -g
On Thursday 29 January 2009, Hasso Tepper wrote:
Linking CXX shared module ../../../lib/kded_phononserver.so
cd /home/kde-devel/kde/build/KDE/kdebase/runtime/phonon/kded-module
/usr/pkg/bin/cmake -E cmake_link_script
CMakeFiles/kded_phononserver.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC
David Faure wrote:
Why is PULSEAUDIO_LIBRARY not set? I see that
kdelibs/cmake/modules/FindPulseAudio.cmake sets it. Is your kdelibs
uptodate?
Damn, I forgot to mention that it's a 4.2 branch. The branch itself is
uptodate, but FindPulseAudio.cmake is in kdebase/runtime/cmake/modules/.
On Thu, 29 Jan 2009 12:07:51 +0100, David Faure wrote:
On Thursday 29 January 2009, Hasso Tepper wrote:
Linking CXX shared module ../../../lib/kded_phononserver.so
cd /home/kde-devel/kde/build/KDE/kdebase/runtime/phonon/kded-module
/usr/pkg/bin/cmake -E cmake_link_script
On Thursday 29 January 2009, Max Brazhnikov wrote:
On Thu, 29 Jan 2009 12:07:51 +0100, David Faure wrote:
On Thursday 29 January 2009, Hasso Tepper wrote:
Linking CXX shared module ../../../lib/kded_phononserver.so
cd /home/kde-devel/kde/build/KDE/kdebase/runtime/phonon/kded-module
Alexander Neundorf wrote:
I haven't looked at the file yet, but it seems pkgconfig is used and
the results are directly put into the variables.
Yeah.
As you see, this is bad.
Instead pkgconfig should be used only optionally, and the results
should be used only as hints for
On Thursday 29 January 2009 1:00:58 pm Alexander Neundorf wrote:
On Thursday 29 January 2009, Max Brazhnikov wrote:
On Thu, 29 Jan 2009 12:07:51 +0100, David Faure wrote:
On Thursday 29 January 2009, Hasso Tepper wrote:
Linking CXX shared module ../../../lib/kded_phononserver.so
cd
On Wed, 26 Nov 2008, Brad King wrote:
Boudewijn Rempt wrote:
macro_optional_find_package(OpenEXR)
[snip]
target_link_libraries(exrthumbnail ${KDE4_KIO_LIBS} ${OPENEXR_LIBRARIES})
Please add a line just before the link command:
message(OPENEXR_LIBRARIES=[${OPENEXR_LIBRARIES}])
On Thu, 27 Nov 2008, Boudewijn Rempt wrote:
On Wed, 26 Nov 2008, Brad King wrote:
Boudewijn Rempt wrote:
macro_optional_find_package(OpenEXR)
[snip]
target_link_libraries(exrthumbnail ${KDE4_KIO_LIBS}
${OPENEXR_LIBRARIES})
Please add a line just before the link command:
On Thu, Nov 27, 2008 at 9:23 AM, Boudewijn Rempt [EMAIL PROTECTED] wrote:
Aw, some discussion on irc pointed to the possiblity that these
find modules just got broken when they were ported use some 2.6.2
functionality, and may be broken on all systems. (probably there aren't
many kdelibs
On Thursday 27 November 2008, Boudewijn Rempt wrote:
On Thu, 27 Nov 2008, Boudewijn Rempt wrote:
On Wed, 26 Nov 2008, Brad King wrote:
Boudewijn Rempt wrote:
macro_optional_find_package(OpenEXR)
[snip]
target_link_libraries(exrthumbnail ${KDE4_KIO_LIBS}
macports in my case and are located in /opt/local/lib.
This used to be no problem, but now the -L/opt/local/lib line is missing,
which gives linker errors, first in kdebase:
Linking CXX shared module ../../../lib/exrthumbnail.so
ld: library not found for -lIlmImf
collect2: ld returned 1 exit status
path seems wrong. Most
dependencies come from macports in my case and are located in /opt/local/lib.
This used to be no problem, but now the -L/opt/local/lib line is missing,
which gives linker errors, first in kdebase:
Linking CXX shared module ../../../lib/exrthumbnail.so
ld: library
On Wed, 26 Nov 2008, Brad King wrote:
Are there any other warnings produced by CMake, such as CMP0003?
No...
Try
running
make VERBOSE=1
and post the actual link line that fails.
Linking CXX shared module ../../../lib/exrthumbnail.so
cd
Boudewijn Rempt wrote:
On Wed, 26 Nov 2008, Brad King wrote:
Are there any other warnings produced by CMake, such as CMP0003?
No...
Try
running
make VERBOSE=1
and post the actual link line that fails.
Linking CXX shared module ../../../lib/exrthumbnail.so
cd
${SERVICES_INSTALL_DIR})
endif(OPENEXR_FOUND)
It's in the $OPENEXR_LIBRARIES -- though I notice I've got the same problem
with lcms in koffice/pigment.
--
Boudewijn Rempt | http://www.valdyas.org
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https
On Friday 05 September 2008 08:29:05 Thiago Macieira wrote:
Michael Jansen wrote:
That fails because /usr/lib64 is not added with -L .
It shouldn't have to be. If it's the platform default, it should be
automatic.
Ok. I found the problem. It was the GraphicsMagick library for me
I hate to say it but it is probably a good idea to ignore my ramblings in such
cases for some days.
I think i completely understand the problem now.
We use --fatal-warnings which means that warning skipping incompatible
/usr/lib/libGL.so when searching for -lGL becomes an error and the linker
Michael Jansen wrote:
On Friday 05 September 2008 08:29:05 Thiago Macieira wrote:
Michael Jansen wrote:
That fails because /usr/lib64 is not added with -L .
It shouldn't have to be. If it's the platform default, it should be
automatic.
But it isn't. If i change -lGL in
On Friday 05 September 2008 08:29:05 Thiago Macieira wrote:
Michael Jansen wrote:
That fails because /usr/lib64 is not added with -L .
It shouldn't have to be. If it's the platform default, it should be
automatic.
But it isn't. If i change -lGL in ./CMakeFiles/kritagmagickimport.dir/link.txt
collect2: ld returned 1 exit status
make[2]: *** [lib/libkritagmagickexport.so] Error 1
It gets pretty messed up when pasted into the mail :-(
The problem is that cmake correctly find the opengl lib under
/usr/lib64/libGL.so. The message from cmake and CMakeCache.txt both show this
path. All
On Monday 07 July 2008 11:51:21 am Alexander Neundorf wrote:
I think we can fix this for KDE 4.2 with cmake 2.6.
What do we do in the meantime ?
We could add ${KDE4_KDECORE_LIBRARY} (which comes with the full path and
features the same name as the one from KDE3) as a direct dependency for all
On Sunday 06 July 2008 07:45:46 pm Thiago Macieira wrote:
David Johnson wrote:
target_link_libraries(kfind ${KDE4_KDE3SUPPORT_LIBS} )
This results in the the following library
locations: -L/usr/local/lib/qt4 -L/usr/local/lib -L/usr/local/kde4/lib
However, changing that line to add a
David Johnson wrote:
On Sunday 06 July 2008 07:45:46 pm Thiago Macieira wrote:
David Johnson wrote:
target_link_libraries(kfind ${KDE4_KDE3SUPPORT_LIBS} )
This results in the the following library
locations: -L/usr/local/lib/qt4 -L/usr/local/lib
-L/usr/local/kde4/lib
However, changing
On Monday 07 July 2008, Thiago Macieira wrote:
David Johnson wrote:
On Sunday 06 July 2008 07:45:46 pm Thiago Macieira wrote:
David Johnson wrote:
target_link_libraries(kfind ${KDE4_KDE3SUPPORT_LIBS} )
This results in the the following library
locations: -L/usr/local/lib/qt4
1 - 100 of 219 matches
Mail list logo
