Difference between revisions of "Getting Started/Build/Distributions/FreeBSD"

Jump to: navigation, search
(Creating a page to describe build quirks for KDE4 on FreeBSD)
 
 
(50 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 +
 
{{KDE4}}
 
{{KDE4}}
  
 +
This page focuses on building KDE SC '''trunk''' on FreeBSD. For building and using stable KDE SC releases on FreeBSD, you should use the ports collection. See the [http://freebsd.kde.org/ports.php KDE/FreeBSD website] for more information.
  
==Required Ports==
+
==Required ports==
* devel/dbus (version 1.0.2 adequate as of Apr 19)
+
* devel/boost-python (for pimlibs)
* devel/cmake (version 2.4p6 adequate as of Apr 19)
+
* devel/cmake
 +
* devel/dbus
 +
* devel/git
 
* devel/subversion
 
* devel/subversion
* (expand as needed, this is a wiki :)
+
* graphics/libungif (for libs)
 +
* misc/shared-mime-info (for libs)
 +
* multimedia/libxine (for runtime, or configure with KDE4_DISABLE_MULTIMEDIA)
 +
* security/gpgme (for pimlibs)
 +
* textproc/libxslt
 +
* textproc/redland (for support/soprano)
 +
* x11/xorg
 +
* x11-toolkits/shared-desktop-ontologies
  
 
==Differences from the normal build process==
 
==Differences from the normal build process==
The page on [[http://techbase.kde.org/Getting_Started/Build/KDE4|building KDE4]] trunk makes a few assumptions about your environment. Note that FreeBSD's dbus and cmake ports will work (so those sections can be skipped).
+
The page on [[Getting_Started/Build|building KDE SC 4]] trunk makes a few assumptions about your environment. Note that FreeBSD's dbus and cmake ports will work (so those sections can be skipped).
 +
 
 +
Sometimes, building with '''make''' can fail on some modules. You should try using '''gmake''' instead.
 +
 
 +
==Using kdesrc-build==
 +
The [http://kdesrc-build.kde.org/ kdesrc-build] script can be used on FreeBSD. Note that if there are errors building qt-copy or libs, look at the issues below and fix them, then continue the build using kdesrc-build.
  
 
==Errors compiling qt-copy==
 
==Errors compiling qt-copy==
; Even when I tell it to, qt-copy is not compiling with dbus support
+
; My build of qt-copy is failing when I have Qt 3 from ports installed.
This is related to the test app for dbus in qt-copy not linking due to a pthreads dependency in libdbus on FreeBSD. To fix it go to: (builddir)/qt-copy/config.tests/unix/dbus . Then manually run "g++ dbus.o -lpthread -ldbus-1 -L/usr/local/lib -o dbus".
+
For some reason, the configure system will sometimes put -I/usr/local/include (which contains the ports version of Qt 3 headers) into the general CXXFLAGS variable. Note that there is an INCPATH variable for these include paths which should also contain -I/usr/local/include. The difference is in the compile line; CXXFLAGS's appears first, whereas the paths in INCPATH are ordered properly such that the local (current build) headers are checked first. You need to go into the directory where the build is failing (use the previous lines before the error message), and open the Makefile. You should see the the -I/usr/local/include line in the CXXFLAGS line, and you can safetly remove it '''if''' there is a -I/usr/local/include line in INCPATH.
That should generate the "dbus" file, and you should be able to continue your qt build as you left off, building dbus this time
+
This seems to usually happen in build_dir/qt-copy/src/plugins/sqldrivers/psql/Makefile.
 +
 
 +
==Errors compiling kdesupport==
 +
; System-wide Qt 4 keeps being found instead of qt-copy
 +
Sometimes, /usr/local/bin/qmake-qt4 insists on being found instead of qt-copy's qmake, which in turn makes cmake use the system-wide Qt during compilation. If everything else fails, you can pass -DQT_QMAKE_EXECUTABLE=/your/path/qmake to cmake.
  
==Errors compiling kdelibs==
+
; Cannot link to polkit-dbus
; kdelibs wont compile, complaining that it can't find qdbus
+
If all polkit-related ports are correctly installed and the error persists, you most likely need to export LIBRARY_PATH and include /usr/local/lib in it.
See the above question on dbus not compiling (even if you told it to compile). If QT can't find the dbus libs, it silently fails and will continue to build without dbus.
+

Latest revision as of 17:26, 13 July 2012

Ktip.png
 
Tip
Note: This page is about KDE 4. It isn't applicable for KDE 3 development.

This page focuses on building KDE SC trunk on FreeBSD. For building and using stable KDE SC releases on FreeBSD, you should use the ports collection. See the KDE/FreeBSD website for more information.

Contents

[edit] Required ports

  • devel/boost-python (for pimlibs)
  • devel/cmake
  • devel/dbus
  • devel/git
  • devel/subversion
  • graphics/libungif (for libs)
  • misc/shared-mime-info (for libs)
  • multimedia/libxine (for runtime, or configure with KDE4_DISABLE_MULTIMEDIA)
  • security/gpgme (for pimlibs)
  • textproc/libxslt
  • textproc/redland (for support/soprano)
  • x11/xorg
  • x11-toolkits/shared-desktop-ontologies

[edit] Differences from the normal build process

The page on building KDE SC 4 trunk makes a few assumptions about your environment. Note that FreeBSD's dbus and cmake ports will work (so those sections can be skipped).

Sometimes, building with make can fail on some modules. You should try using gmake instead.

[edit] Using kdesrc-build

The kdesrc-build script can be used on FreeBSD. Note that if there are errors building qt-copy or libs, look at the issues below and fix them, then continue the build using kdesrc-build.

[edit] Errors compiling qt-copy

My build of qt-copy is failing when I have Qt 3 from ports installed.

For some reason, the configure system will sometimes put -I/usr/local/include (which contains the ports version of Qt 3 headers) into the general CXXFLAGS variable. Note that there is an INCPATH variable for these include paths which should also contain -I/usr/local/include. The difference is in the compile line; CXXFLAGS's appears first, whereas the paths in INCPATH are ordered properly such that the local (current build) headers are checked first. You need to go into the directory where the build is failing (use the previous lines before the error message), and open the Makefile. You should see the the -I/usr/local/include line in the CXXFLAGS line, and you can safetly remove it if there is a -I/usr/local/include line in INCPATH. This seems to usually happen in build_dir/qt-copy/src/plugins/sqldrivers/psql/Makefile.

[edit] Errors compiling kdesupport

System-wide Qt 4 keeps being found instead of qt-copy

Sometimes, /usr/local/bin/qmake-qt4 insists on being found instead of qt-copy's qmake, which in turn makes cmake use the system-wide Qt during compilation. If everything else fails, you can pass -DQT_QMAKE_EXECUTABLE=/your/path/qmake to cmake.

Cannot link to polkit-dbus

If all polkit-related ports are correctly installed and the error persists, you most likely need to export LIBRARY_PATH and include /usr/local/lib in it.


This page was last modified on 13 July 2012, at 17:26. This page has been accessed 38,019 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal