Getting Started/Build/KDE4 (bn IN) - Revision history

AnneW at 15:57, 14 July 2012

2012-07-14T15:57:28Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:56:54Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:46:54Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:46, 29 June 2011
			
Line 118:
Line 118:
    
  In Kubuntu 7.04 (Feisty) and Debian (Testing/Unstable) the build dependencies you need are installed with:   In Kubuntu 7.04 (Feisty) and Debian (Testing/Unstable) the build dependencies you need are installed with:
− <code> + <syntaxhighlight lang="text">
  sudo aptitude install build-essential cdbs debhelper cmake \   sudo aptitude install build-essential cdbs debhelper cmake \
  libxml2-dev libxslt1-dev libbz2-dev libclucene-dev librdf-dev \   libxml2-dev libxslt1-dev libbz2-dev libclucene-dev librdf-dev \
Line 133:
Line 133:
    
  In Kubuntu 7.10 (Gutsy) and Debian unstable you also have to add:   In Kubuntu 7.10 (Gutsy) and Debian unstable you also have to add:
− <code> + <syntaxhighlight lang="text">
  sudo aptitude install dbus-x11  libqt4-dev libqca2-dev libeigen-dev \   sudo aptitude install dbus-x11  libqt4-dev libqca2-dev libeigen-dev \
  libstreamanalyzer-dev libsoprano-dev libstrigiqtdbusclient-dev \   libstreamanalyzer-dev libsoprano-dev libstrigiqtdbusclient-dev \
Line 141:
Line 141:
    
  For a fully functional API documentation framework you also need:   For a fully functional API documentation framework you also need:
− <code> + <syntaxhighlight lang="text">
  sudo aptitude install graphviz   sudo aptitude install graphviz
  </code>   </code>
Line 186:
Line 186:
    
  The packages you will need to install are:   The packages you will need to install are:
− <code> + <syntaxhighlight lang="text">
  xorg-x11-devel   xorg-x11-devel
  libxml2-devel     libxml2-devel  
Line 214:
Line 214:
    
  For openSUSE 10.2 and newer do:   For openSUSE 10.2 and newer do:
− <code> + <syntaxhighlight lang="text">
  sudo zypper service-add http://software.opensuse.org/download/KDE:/KDE4/openSUSE_10.2 KDE4-102   sudo zypper service-add http://software.opensuse.org/download/KDE:/KDE4/openSUSE_10.2 KDE4-102
  </code>   </code>
    
  For older versions of SUSE Linux do:   For older versions of SUSE Linux do:
− <code> + <syntaxhighlight lang="text">
  su   su
  installation_sources -a http://software.opensuse.org/download/KDE:/KDE4/[YOUR SUSE LINUX VERSION]   installation_sources -a http://software.opensuse.org/download/KDE:/KDE4/[YOUR SUSE LINUX VERSION]
Line 225:
Line 225:
    
  Now install the following packages:   Now install the following packages:
− <code> + <syntaxhighlight lang="text">
  cmake   cmake
  dbus-1-devel   dbus-1-devel
Line 239:
Line 239:
    
  And for fully functional apidox framework you also need:   And for fully functional apidox framework you also need:
− <code> + <syntaxhighlight lang="text">
  graphviz   graphviz
  </code>   </code>
Line 602:
Line 602:
  * Here you need the libungif library, otherwise you will get an error message like "<tt>Could NOT find GIF</tt>".   * Here you need the libungif library, otherwise you will get an error message like "<tt>Could NOT find GIF</tt>".
  * Qt-4.3 upgrade: if you get a link error in kjsembed talking about QScriptEngine, edit CMakeCache.txt in kdelibs and remove the lines that talk about QT_QTUITOOLS_LIBRARY, then type make again (that static library has a new dependency, and the cmake code that adds it needs to run).   * Qt-4.3 upgrade: if you get a link error in kjsembed talking about QScriptEngine, edit CMakeCache.txt in kdelibs and remove the lines that talk about QT_QTUITOOLS_LIBRARY, then type make again (that static library has a new dependency, and the cmake code that adds it needs to run).
− * if you get <code>CMake Error: KDE Requires Qt to be built with SSL support + * if you get <syntaxhighlight lang="text">CMake Error: KDE Requires Qt to be built with SSL support
  </code>, install openssl-devel, remove CMakeCache.txt and re-compile QT.   </code>, install openssl-devel, remove CMakeCache.txt and re-compile QT.
− * if you get <code>kdelibs/kimgio/ico.cpp:188: undefined reference to `QImage::jumpTable()'</code> it means you compiled QT without QT3 support(no, linking to a true QT3 install won't work) + * if you get <syntaxhighlight lang="text">kdelibs/kimgio/ico.cpp:188: undefined reference to `QImage::jumpTable()'</code> it means you compiled QT without QT3 support(no, linking to a true QT3 install won't work)
− * if none of the errors above match yours, you might just try a quick'n'dirty <code>make clean</code> in kdelibs. + * if none of the errors above match yours, you might just try a quick'n'dirty <syntaxhighlight lang="text">make clean</code> in kdelibs.
    
  == kdepimlibs ==   == kdepimlibs ==
Line 722:
Line 722:
  Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:   Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:
    
− <code> + <syntaxhighlight lang="text">
  add_subdirectory(libkdegames)   add_subdirectory(libkdegames)
  add_subdirectory(libkmahjongg)   add_subdirectory(libkmahjongg)
Line 760:
Line 760:
    
  For example for RH/Fedora based distros:   For example for RH/Fedora based distros:
− <code>   + <syntaxhighlight lang="text">  
    #%PAM-1.0     #%PAM-1.0
    auth       include      system-auth     auth       include      system-auth



Neverendingo: Text replace - "" to ""

2011-06-29T20:41:00Z
Text replace - "<code bash>" to "<syntaxhighlight lang="bash">"

				
				
				
				
			
			← Older revision
			Revision as of 20:41, 29 June 2011
			
Line 36:
Line 36:
  In Ark Linux, the build dependencies you need are installed with:   In Ark Linux, the build dependencies you need are installed with:
    
− <code bash> + <syntaxhighlight lang="bash">
  apt-get install devel-core libxml-devel libxslt-devel bzip2-devel \   apt-get install devel-core libxml-devel libxslt-devel bzip2-devel \
  clucene-core-devel librdf-devel shared-mime-info xorg-Mesa-libGL-devel \   clucene-core-devel librdf-devel shared-mime-info xorg-Mesa-libGL-devel \
Line 50:
Line 50:
  In Arch Linux you need to install the following packages:   In Arch Linux you need to install the following packages:
    
− <code bash> + <syntaxhighlight lang="bash">
  pacman -Sy subversion bzip2 libxslt libxml2 \   pacman -Sy subversion bzip2 libxslt libxml2 \
  shared-mime-info mesa boost dbus openssl \   shared-mime-info mesa boost dbus openssl \
Line 59:
Line 59:
    
  If you want to use qt4 from the Arch Linux repository you can install it with:   If you want to use qt4 from the Arch Linux repository you can install it with:
− <code bash> + <syntaxhighlight lang="bash">
  pacman -Sy qt4   pacman -Sy qt4
  </code>   </code>
Line 71:
Line 71:
  Some of the required packages for building KDE4 on Fedora 7 or higher:   Some of the required packages for building KDE4 on Fedora 7 or higher:
    
− <code bash> + <syntaxhighlight lang="bash">
  yum install clucene-core-devel libxml-devel libxslt-devel \   yum install clucene-core-devel libxml-devel libxslt-devel \
  dbus-devel boost-devel bzip2-devel openssl-devel alsa-lib-devel \   dbus-devel boost-devel bzip2-devel openssl-devel alsa-lib-devel \
Line 88:
Line 88:
    
  Some optional packages for koffice support:   Some optional packages for koffice support:
− <code bash> + <syntaxhighlight lang="bash">
  yum install qca2-devel gsl-devel freeglut-devel \   yum install qca2-devel gsl-devel freeglut-devel \
  GraphicsMagick-c++-devel GraphicsMagick-devel   GraphicsMagick-c++-devel GraphicsMagick-devel
Line 173:
Line 173:
    
  In openSUSE 10.2 and newer, you can install packages using [http://en.opensuse.org/Zypper Zypper]:   In openSUSE 10.2 and newer, you can install packages using [http://en.opensuse.org/Zypper Zypper]:
− <code bash> + <syntaxhighlight lang="bash">
  sudo zypper install <package-name>   sudo zypper install <package-name>
  </code>   </code>
    
  In older releases of SUSE, you can use YaST:   In older releases of SUSE, you can use YaST:
− <code bash> + <syntaxhighlight lang="bash">
  su   su
  yast -i <packagename>   yast -i <packagename>
Line 257:
Line 257:
  We need to allow the following keyword masked ebuilds.   We need to allow the following keyword masked ebuilds.
           
− <code bash> + <syntaxhighlight lang="bash">
  echo 'dev-util/cmake' >> /etc/portage/package.keywords   echo 'dev-util/cmake' >> /etc/portage/package.keywords
  echo 'dev-cpp/clucene' >> /etc/portage/package.keywords   echo 'dev-cpp/clucene' >> /etc/portage/package.keywords
Line 264:
Line 264:
  Make sure you have set the berkdb USE flag for redland, otherwise nepomuk won't work.   Make sure you have set the berkdb USE flag for redland, otherwise nepomuk won't work.
    
− <code bash> + <syntaxhighlight lang="bash">
  echo 'dev-libs/redland berkdb' >> /etc/portage/package.use   echo 'dev-libs/redland berkdb' >> /etc/portage/package.use
  echo 'x11-libs/qt accessibility' >> /etc/portage/package.use   echo 'x11-libs/qt accessibility' >> /etc/portage/package.use
Line 271:
Line 271:
  These are the packages you will need to emerge, I included the update option into the emerge command so you will not re-emerge anything that you might already have installed.   These are the packages you will need to emerge, I included the update option into the emerge command so you will not re-emerge anything that you might already have installed.
    
− <code bash> + <syntaxhighlight lang="bash">
  emerge -avu 'sys-devel/gcc' \   emerge -avu 'sys-devel/gcc' \
     'dev-util/subversion' \      'dev-util/subversion' \
Line 303:
Line 303:
    
  Also you can install the KDE 4 packages directly via     Also you can install the KDE 4 packages directly via  
− <code bash> + <syntaxhighlight lang="bash">
  emerge -a <packagename>   emerge -a <packagename>
  </code>   </code>
    
  To get the things you need, [http://gentoo-wiki.com/TIP_Overlays#Layman install layman] and then pull in the "kde" overlay (which contains experimental KDE ebuilds):     To get the things you need, [http://gentoo-wiki.com/TIP_Overlays#Layman install layman] and then pull in the "kde" overlay (which contains experimental KDE ebuilds):  
− <code bash> + <syntaxhighlight lang="bash">
  layman -a kde   layman -a kde
  </code>   </code>
Line 320:
Line 320:
  In Mandriva the build dependencies you need are installed with:   In Mandriva the build dependencies you need are installed with:
    
− <code bash> + <syntaxhighlight lang="bash">
  urpmi gcc-c++ cmake libxml2-devel libbzip2_1-devel \   urpmi gcc-c++ cmake libxml2-devel libbzip2_1-devel \
  libclucene0-devel liblrdf2-devel libmesagl1-devel \   libclucene0-devel liblrdf2-devel libmesagl1-devel \
Line 345:
Line 345:
    
  === Option 1: Command Line ===   === Option 1: Command Line ===
− <code bash> + <syntaxhighlight lang="bash">
  useradd -m kde-devel   useradd -m kde-devel
  passwd kde-devel   passwd kde-devel
Line 363:
Line 363:
  Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).      Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).   
  To make it run, you have to open a new bash or to execute     To make it run, you have to open a new bash or to execute  
− <code bash> + <syntaxhighlight lang="bash">
  source ~/.bashrc   source ~/.bashrc
  </code>   </code>
Line 373:
Line 373:
  === Switching to the New User ===   === Switching to the New User ===
  Switch to the user kde-devel: (don't forget the dash)   Switch to the user kde-devel: (don't forget the dash)
− <code bash> + <syntaxhighlight lang="bash">
  ssh -X kde-devel@localhost   ssh -X kde-devel@localhost
  </code>   </code>
Line 389:
Line 389:
    
  If you don't have root privileges and your system supports the changing of your own shell with the <tt>chsh</tt> application, then you could try to change your shell to {{path|/bin/bash}} by using:   If you don't have root privileges and your system supports the changing of your own shell with the <tt>chsh</tt> application, then you could try to change your shell to {{path|/bin/bash}} by using:
− <code bash> + <syntaxhighlight lang="bash">
  chsh -s /bin/bash kde-devel   chsh -s /bin/bash kde-devel
  </code>   </code>
Line 633:
Line 633:
  :This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.   :This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.
    
− You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <code bash>cd kdebase</code> with <code bash>cd kdebase/runtime</code> in the recipe below. + You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <syntaxhighlight lang="bash">cd kdebase</code> with <syntaxhighlight lang="bash">cd kdebase/runtime</code> in the recipe below.
    
  === The Recipe ===   === The Recipe ===
Line 699:
Line 699:
    
  Another, even easier method involves downloading this [[Doxyfile]] to your local system. Then simply change directory to where you want to create the documentation and run   Another, even easier method involves downloading this [[Doxyfile]] to your local system. Then simply change directory to where you want to create the documentation and run
− <code bash> + <syntaxhighlight lang="bash">
  % doxygen /path/to/Doxyfile   % doxygen /path/to/Doxyfile
  </code>   </code>
Line 709:
Line 709:
    
  For example:   For example:
− <code bash> + <syntaxhighlight lang="bash">
  cs kdesupport # cs is not a typo   cs kdesupport # cs is not a typo
  svn up   svn up
Line 733:
Line 733:
  So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:   So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:
    
− <code bash> + <syntaxhighlight lang="bash">
  cs KDE   cs KDE
  svn co -N kdegames # The -N switch performs a non-recursive checkout   svn co -N kdegames # The -N switch performs a non-recursive checkout



Jospoortvliet: /* Arch Linux */
2008-04-23T07:54:11Z
‎Arch Linux

				
				
				
				
			
			← Older revision
			Revision as of 07:54, 23 April 2008
			
Line 55:
Line 55:
  pkgconfig xine-lib clucene   pkgconfig xine-lib clucene
  </code>   </code>
  + 
  + Ensure you don't have Soprano installed (pacman -R soprano) because Nepomuk won't detect the soprano in kdesupport and thus not build.
    
  If you want to use qt4 from the Arch Linux repository you can install it with:   If you want to use qt4 from the Arch Linux repository you can install it with:



Jospoortvliet: /* Arch Linux */
2008-04-23T07:53:31Z
‎Arch Linux

				
				
				
				
			
			← Older revision
			Revision as of 07:53, 23 April 2008
			
Line 55:
Line 55:
  pkgconfig xine-lib clucene   pkgconfig xine-lib clucene
  </code>   </code>
−  
− You might need to get Soprano from the testing repository (you need at least version 2.0.1). For this, enable the testing repository in /etc/pacman.conf and do:  
− <code bash>  
− pacman -Sy soprano  
− </code>  
− Now you can disable the testing repository again (if you prefer to keep your system stable).  
    
  If you want to use qt4 from the Arch Linux repository you can install it with:   If you want to use qt4 from the Arch Linux repository you can install it with:



Jospoortvliet: /* Arch Linux */
2008-04-23T07:43:35Z
‎Arch Linux

				
				
				
				
			
			← Older revision
			Revision as of 07:43, 23 April 2008
			
Line 55:
Line 55:
  pkgconfig xine-lib clucene   pkgconfig xine-lib clucene
  </code>   </code>
  + 
  + You might need to get Soprano from the testing repository (you need at least version 2.0.1). For this, enable the testing repository in /etc/pacman.conf and do:
  + <code bash>
  + pacman -Sy soprano
  + </code>
  + Now you can disable the testing repository again (if you prefer to keep your system stable).
    
  If you want to use qt4 from the Arch Linux repository you can install it with:   If you want to use qt4 from the Arch Linux repository you can install it with:





Dhaumann: /* HAL */
2008-01-29T19:50:17Z
‎HAL

				
				
				
				
			
			← Older revision
			Revision as of 19:50, 29 January 2008
			
Line 502:
Line 502:
  {{tip|You can use qdbusviewer to see if you have org.freedesktop.hal. If not, you might need a newer version of hal. If you have org.freedesktop.hal, you probably don't need to, and don't ''want'' to, roll your own HAL.}}   {{tip|You can use qdbusviewer to see if you have org.freedesktop.hal. If not, you might need a newer version of hal. If you have org.freedesktop.hal, you probably don't need to, and don't ''want'' to, roll your own HAL.}}
    
− If your system requires you to build a newer version of HAL, there's a decent chance you'll need to build other stuff as well, some of which may not be straight forward. Since this should only be required for older distros, instructions are on [[Getting_Started/Build/HAL| a separate page]]. + If your system requires you to build a newer version of HAL, there's a decent chance you'll need to build other stuff as well, some of which may not be straight forward. However, this should only be required for older distros.
    
  == kdesupport ==   == kdesupport ==





Kushaldas at 09:19, 9 January 2008
2008-01-09T09:19:21Z


				
				
				
				
			
			← Older revision
			Revision as of 09:19, 9 January 2008
			
Line 14:
Line 14:
  }}   }}
    
− == Abstract == + == সারসংক্ষেপ ==
    
  এই সহায়িকা কি ভাবে ট্রান্ক থেকে KDE নিয়ে লিনাক্স/বিসডি সিস্টেমে তা দেখায়।   এই সহায়িকা কি ভাবে ট্রান্ক থেকে KDE নিয়ে লিনাক্স/বিসডি সিস্টেমে তা দেখায়।



Kushaldas: started writing the page in bengali
2008-01-08T17:23:02Z
started writing the page in bengali
Show changes

← Older revision		Revision as of 15:57, 14 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Getting_Started/Build/KDE4}}~~

	{{TutorialBrowser\|		{{TutorialBrowser\|