Message: previous - next
Month: February 2011

Re: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?

From: "David C. Rankin" <drankinatty@...>
Date: Wed, 16 Feb 2011 11:10:50 -0600
On 02/16/2011 10:06 AM, Timothy Pearson wrote:
> <snip>
>'re using CMake to build kdelibs/kdebase, correct?  You can't mix
> CMake and Automake, it won't work.
> If kdeaccessibility does not yet have CMake available, then it can't be
> built on your system at this time.  We need more people to help with the
> CMake port (from what I hear it is relatively simple/mind numbing work).
> Tim

  There is no CMake for a majority of the Trinity modules:

11:07 archangel:~/arch/trinity> for i in $(ls); do [[ -f $i/CMakeLists.txt ]] &&
echo " CMake   -- $i" || echo "NO CMake -- $i"; done | sort
 CMake   -- kdebase
 CMake   -- kdelibs
 CMake   -- kdevelop
 CMake   -- kdewebdev
NO CMake -- applications
NO CMake -- dependencies
NO CMake -- kde-common
NO CMake -- kde-i18n
NO CMake -- kdeaccessibility
NO CMake -- kdeaddons
NO CMake -- kdeadmin
NO CMake -- kdeartwork
NO CMake -- kdebindings
NO CMake -- kdeedu
NO CMake -- kdegames
NO CMake -- kdegraphics
NO CMake -- kdemultimedia
NO CMake -- kdenetwork
NO CMake -- kdepim
NO CMake -- kdesdk
NO CMake -- kdetoys
NO CMake -- kdeutils
NO CMake -- konstruct
NO CMake -- libraries

  I don't know cmake from shinola, but if you have a cheat-sheet on how to
convert things to cmake, I'm happy to peck it into the keyboard. Something like
"A Dummy's Guild to Port Trinity to CMake"?

David C. Rankin, J.D.,P.E.