Updated the GitHub page with the following:
EFL 1.20.2
Python-EFL 1.20.0
Enlightenment DR 0.21.9
Ephoto 1.5
Terminology 1.1.0

Everything seems to work under -current.

1 members found this post helpful.

Hi guys, I've been following 'E' development since 2014. Originally there was Slacke17, which worked well, but then there was talk about requirement for SystemD.
Can Slackware64 14.2 multilib use 'E' without SystemD?
This thread seems to build everything separately. Is there still a Slacke17 complete package install available, or does everything have to be built separately?
I don't use sbopkg but sbotools (which uses SBo also), and has an ncurses interface sboui. Can I build 'E' from SBo, or is it better to clone the git?
I currently use WindowMaker or FVWM because KDE is hanging my NetGear N150 at times. Does econnman support that dongle or will I still use WICD?
Thanks for the advice. Cheers

Both slackENLIGHTENMENT (https://github.com/ryanpcmcquen/slackENLIGHTENMENT) and the version of 'E' at SBo do not require systemd.

Do I still need to build with --systemD? or are the default slackware packages already aware?
Why does the SBo packages of efl say that it requires Bullet? Is it used by the graphics of 'E', its README descriptioin does NOT seem like it is connected in anyway.
Can I use sbotools to build efl, terminology, python-efl, enlightenment from SBo and get the same results as the git?
SBo doesn't seem to have ephoto or rage, are their slackbuilds on git which can be used to build these?
Thanks, BrianA_MN

The build scripts already have the configure flags set. I have not tested building without 'bullet', but I am pretty sure it is required.

OK, Can I use sbotools to build efl, terminology, python-efl, enlightenment from SBo, modify the blacklist and get the same results as the git?
SBo doesn't seem to have ephoto or rage, are their slackbuilds on git which can be used to build these? Cheers, BrianA_MN

I don't use sbotools, but slackENLIGHTENMENT has very up-to-date versions of Enlightenment, SBo, has older versions. Just use slackENLIGHTENMENT.

Sbotools is simply another SBo tool, which still uses the slackbuild from SBo, downloads the source, and creates a package for installation.

I've compared the git and SBo slackbuilds on the SBo it is version specific and doesn't have the -1sEL tag, which means the blacklist would not work. Additionally, there are some differences with the configure build enable and disable options
for git efl:
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--enable-harfbuzz \
--enable-fb \
--disable-tslib \
--disable-static \
--disable-systemd \
--with-profile=release \
--enable-lua-old \
--enable-image-loader-xyz=auto \
--enable-xinput22 \
--enable-multisense \
--build=$ARCH-slackware-linux

for SBo efl:
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--disable-systemd \
--build=$ARCH-slackware-linux


then for git enlightenment.
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--disable-static \
--disable-device-hal \
--enable-device-udev \
--enable-mount-udisks \
--enable-mount-eeze \
--enable-enotify \
--disable-doc \
--build=$ARCH-slackware-linux

for SBo enlightenment
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--disable-static \
--build=$ARCH-slackware-linux

Perhaps these differences are to allow 'E' to built for -current (git) and stable (SBo)?
Appreciate the continued advice. I plan to build with the SBo and see what happens. I'll let you know. I think the build order is still correct though

luajit
bullet
lua
efl
terminology
python-efl
enlightenment

Cheers Brian_MN

SBo is one method of building packages for your system.

For Enlightenment, it is best to not use anything directly from SBo. Rather, use the slackENLIGHTENMENT script, which should be a run once, build everything type of script. It does rely on using sbopkg for a few dependencies from SBo, so if you don't have that, it will bomb out. You might be able to tweak the script to allow it to use sbotools rather than sbopkg (or to not build those packages provided you install them before you start the script).

Once you have sbopkg installed and configured (or tweak the script to use sbotools), you just run sh enlighten-me.sh from within the cloned repo of slackENLIGHTENMENT and sit back and wait for it to do its things.

1 members found this post helpful.

bamunds, I was the maintainer of both for a while (SBo and slackENLIGHTENMENT), and slackENLIGHTENMENT has had a lot more care put into it. Specifically, mats_b_tegner and I (among others) took a lot of time reading upstream's recommended configure flags, it appears that although the SBo version has been updated, it is still a few versions behind, and has not heeded the recommended configure options of upstream.

While trying to build elf I run into an error for shared libraries: libreadline.so.7 I have /usr/lib(&lib64)/libreadline.so.6 & 6.3 but no .7 who creates the .7 extension?

Where are you building from?

I'm compiling this right now. I will update the GitHub page.
/Mats

1 members found this post helpful.

I was building from the directory slackENLIGHTENMENT with the command sh enlighten-me.sh as root.

Again, please remember that this is running on Slackware64 14.2 multilib enabled.
In the past I created a symlink from a needed file to the latest available, would this work to create a symlink of libreadline.so.7 to libreadline.so.6? Which is why I asked the question of what creates the libreadline.so.7?

Additionally, I'm seeing a regular warning for libtool: warning /usr/lib64/libstdc++.la seems to be moved. But if I check with slocate libstdc++.la is both in /usr/lib and /usr/lib64. So why am I getting a warning from libtool or the enlighten-me.sh script? Is it an environment issue?

Cheers

The symlink should fix that. Are you on a full install? The Enlightenment project has had tons of warnings from E18+, they aren't anything for the end user to worry about.