Page MenuHomePhabricator

Enlightenment on OpenBSD
Updated 2,147 Days AgoPublic

You can install Enlightenment on OpenBSD from its port tree or from the official svn repository.

OpenBSD Reported Issues

additional reports:

Realm

Unfortunately the existing EFL/E17 packages are quite outdated and also contain no features, attractive for ordinary users. And the one could decide to build from scratch. The text below could be helpful for maintainers/individuals, who wish to have a latest E-svn running on OpenBSD. Please examine all OpenBSD related "tickets" before report a new issue. All comments/patches/improvements are always welcome!

Beginning

Building the E-svn is quite easy for those, who follow the OpenBSD-current. The rest should first install some packages to satisfy build dependencies. Some of them are strict (like "gmake", "intltool", "automake"), others depend on your requirements (like "librsvg" to get "svg" support). The list also depends on the components you wish to build and install from E-svn tree.

  • Build dependencies (+/-):
    • metaauto - wrapper for gnu auto*
    • libtool - generic shared library support script
    • automake - GNU standards-compliant Makefile generator
    • autoconf - automatically configure source code on many Un*x platforms
    • intltool - internationalization tool
    • gcc
    • gmake
    • subversion
    • libiconv - character set conversion library
    • gettext >= 0.17 - GNU gettext
    • jpeg - IJG's JPEG compression utilities
    • libtasn1 - Abstract Syntax Notation One structure parser library (may be it's optional)
    • lua - (needed for "edje") powerful, light-weight programming language
    • X-server/(xenocara)
    • imlib2 - image manipulation library (though you can build it from E-svn too)
  • Optional dependencies
    • a lot of. Depends on your "build from E-svn list". Some even have a substitutions (gnuTLS/openSSL). Below is just a sample list, no restrictions:

      gnuTLS/openSSL, png, librsvg, bison, glib2, doxygen, SDL*, pango, cairo, tiff, libungif, fribidi(UTF-8 support), libnotify, dbus, mpd/libmpd, etc...

It could be a nice idea to install "bash" and build E with it, instead of the default "ksh". Please take a look at the "gcc". Note, that the "default" gcc in OpenBSD has options/version, which differ from the ones used for ports/packages. This could have an impact on a various build options, most notable is the support/linking of "pthreads". The default OpenBSD compiler has: "Thread model: single, gcc version 3.3.5 (propolice)". Packaged versions of "gcc4" have posix thread model and a way different configuration parameters. You can build E-svn with any modern compiler, including the one shipped by default in OpenBSD, but anyway, YOU HAVE BEEN WARNED! "--disable-pthread" is the most safe option and probably should be used if you're building for a various architectures or if you're cooking the updates for E/EFL ports.

Build routine

Package details

It is recommended to build them in this order.

efl

Efl is a set of packages, namely Eina, Eet, Evas, Ecore, Eo, Embryo and Eio.
The default cryptographic system is OpenSSL, but you can change it to GnuTLS by passing:

./configure --with-crypto=gnutls

Works with build routine.

edje

Works with build routine. Make sure you have a "lua" package installed.

efreet

Works with build routine. Nothing to add.

e_dbus

Works with build routine. Nothing to add.

E17/e

Works with build routine.

If you're following the defaults, all stuff will be in a "/usr/local/". After installation you'd ensure that "/etc/enlightenment/" is present (create a symlink to the $PREFIX/etc/enlightenment) and you should adjust the "/etc/enlightenment/sysactions.conf" file (see the example below):

action:   halt      /sbin/halt -p
action:   reboot    /sbin/reboot
action:   suspend   /usr/sbin/zzz -S
action:   hibernate /usr/sbin/zzz -z
###
# optional, please read the comments.
###
group:   users  allow: *

edje_editor

The same error with compilation of "*.edj" file could happen. Example of error message:

edje_cc -v -id ../data/images -fd ../data/fonts \
        ../data/edje_editor.edc \
        ../data/edje_editor.edj
<stdin>:319: macro "FRAME" requires 7 arguments, but only 5 given
edje_cc: Opening "../data/edje_editor.edc" for input
edje_cc: Parsing input file
gmake[3]: *** [edje_editor.edj] Segmentation fault (core dumped)

The cure is :

> vim edje_editor/data/Makefile.am

desktopdir   = $(datadir)/applications
desktop_DATA = edje_editor.desktop

icondir = $(datadir)/icons
icon_DATA = edje_editor.png

#edje_editor.edj: edje_editor.edc Makefile
#   $(EDJE_CC) $(EDJE_FLAGS) \
#   $(top_srcdir)/data/edje_editor.edc \
#   $(top_builddir)/data/edje_editor.edj

blank.edj: blank.edc Makefile
    $(EDJE_CC) $(EDJE_FLAGS) \
    $(top_srcdir)/data/blank.edc \
    $(top_builddir)/data/blank.edj

and run "./autogen.sh" again. After installation you shout put a valid "edje_editor.edj" file (borrowed from Linux-box probably, or you can fix "edje_editor.edc" and submit a patch to the community) to the installation dir: "$INSTALL_PREFIX/share/edje_editor/edje_editor.edj".

E16

./configure --disable-docs

if you don't want to look at the patches used for existing OpenBSD port and wish to build a good old rocking E16 from E-svn quickly.

Summary

Things are quite easy and straight-forward. You can follow the latest snapshots or current E-svn without too much efforts. Please, don't forget to install a copy into the local empty folder to have an exact list of affected files at least. Don't turn Your system into the scrapyard. Delete an old files/components before a fresh E-svn build.

List of confirmed successful builds

amd64 - confirmed on OpenBSD-current (Oct. 2012)

TODO

  • Eeze (?)
  • Ethumb
  • Elementary (toolkit)
  • Elsa (login manager)

Imported from https://trac.enlightenment.org/e/wiki/OpenBSD
History:
1 dlg 2007-11-16 00:34:23 start documenting where support is up to.
2 dlg 2007-11-16 00:41:27 show how to use the ports
3 dlg 2007-11-16 00:44:03 more text
4 dlg 2007-11-16 00:44:41
5 dlg 2007-11-16 00:49:30 typo
6 lfx 2007-11-16 01:42:13
7 lfx 2007-11-16 01:45:28
8 dlg 2007-11-16 03:27:20 tweaks
9 lfx_ 2007-11-23 12:13:02 EWL bug
10 lfx__ 2007-11-24 13:57:40
11 lfx__ 2007-11-24 14:58:53
12 lfx__ 2007-11-24 15:38:02
13 sda00@himki.net 2007-12-20 05:10:20
14 laurent 2007-12-24 04:25:42 Update the information.
15 mcalamelli 2009-01-03 18:21:19 Moves form bugzilla bugs to with trac tickets, if available
16 sda00@himki.net 2009-11-10 11:26:25
17 sda00@himki.net 2009-11-10 12:04:06
18 sda00@himki.net 2009-11-10 12:20:24
19 sda00@himki.net 2009-11-10 12:43:08
20 sda00@himki.net 2009-11-10 13:10:45
21 sda00@himki.net 2009-11-10 13:27:07
22 sda00@himki.net 2009-11-10 13:53:12
23 sda00@himki.net 2009-11-10 13:54:02
24 sda00@himki.net 2009-11-10 14:30:29
25 sda00@himki.net 2009-11-10 14:33:33
26 sda00@himki.net 2009-11-10 14:36:15
27 sda00@himki.net 2009-11-10 15:05:27
28 sda00@himki.net 2009-11-10 15:12:27
29 sda00@himki.net 2009-11-10 15:23:37
30 sda00@himki.net 2009-11-10 15:26:13
31 sda00@himki.net 2009-11-10 15:49:47
32 sda00@himki.net 2009-11-10 17:51:12
33 sda00@himki.net 2009-11-10 17:51:58
34 sda00@himki.net 2009-11-10 17:54:14
35 sda00@himki.net 2009-11-10 17:58:19
36 sda00@himki.net 2009-11-10 18:00:37
37 sda00@himki.net 2009-11-10 18:03:42
38 sda00@himki.net 2009-11-10 18:33:00
39 sda00@himki.net 2009-11-11 07:58:53
40 sda00@himki.net 2009-11-11 08:02:01
41 sda00@himki.net 2009-11-11 08:07:15
42 sda00@himki.net 2009-11-12 03:51:17
43 sda00@himki.net 2009-11-12 04:55:47
44 sda00@himki.net 2009-11-12 13:13:46
45 sda00@himki.net 2010-05-23 10:41:02
46 vtorri 2012-07-20 14:05:44
47 rustyBSD 2012-08-20 01:47:09 Some updates. I'll reupdate soon
48 rustyBSD 2012-08-21 04:32:22 Update
49 rustyBSD 2012-08-21 11:13:52 reports
50 rustyBSD 2012-08-22 12:36:52 update
51 rustyBSD 2012-08-24 02:04:02 update
52 rustyBSD 2012-08-24 02:13:49 update
53 rustyBSD 2012-08-30 09:51:24 update
54 rustyBSD 2012-11-07 23:50:30 Update
55 rustyBSD 2012-12-15 13:11:53 Update

Last Author
beber
Last Edited
Sep 5 2013, 2:01 PM
Projects
None
Subscribers
None