Has anyone tried using SilentEye on Slackware?
 

Developer Website: http://www.silenteye.org/

It looks like an interesting program, however I can't find a Slackware package for it and src2pkg failed on me (no dependancy info found, possibly missing libraries or poor makefiles it tells me). Looking at the requirements listed, qt4-dev-tools is an umbrella package for a bunch of other stuff in Ubuntu and I'm currently running through all the packages included in that, making sure I have them all.

Any other suggestions?

The default for a cmake build is to create a build directory,
cd build/ && 'cmake ..' && make, and that's what scr2pkg does. Will fail.
(The missing dependencies are headers generated in
silenteye-0.4.1-src/src/ : ui_mainwindow.h etc.)

The proof way is: 1) cd silenteye-0.4.1-src/ && cmake . ( cmake <space> <period> )
2) make


( I did not find any Slackbuild script for silenteye either.)

..

I'm not an expert for cmake-based builds, and I have never used src2pkg or SilentEye, but...

I'd try unzipping the source and running cmake by hand. I think cmake will inform you if dependencies are missing.

Also, have a look at the README_UNIX file mentioned here: http://www.silenteye.org/devenv.html?i3s1
I guess it is included with the source.

Hope this can get you started.

EDIT:
knudfl above has some good advice.
If that's true, you will need to install manually or write your own slackbuild script.
If you want to write your own slackbuild script, slackbuilds.org has some good templates: http://slackbuilds.org/templates/

Thanks for the advice. I've considered learning about writing Slackbuild scripts before but I've never really found a reason to do it until now. All I need is a free afternoon.

I just tried it and works, no additional deps besides what's in standard slackware, but the software has some problems (maybe of youngness) and I think it's not ready for slackbuilding it: seems like the binary has to reside in a folder where the user that launch it must have write permissions (the build folder should be ok too), because it saves its configuration there :o (not talking about the log file position that is hardcoded in the build directory)

also note that its build system doesn't support out of tree builds, so, if you choose to follow the cmake-template.Slackbuild example, use this
don't do this of it won't find some headers
I haven't had a really deep look, but it can be I missed some configuration options or other distros apply some patches to the source to have it usable from /opt or somewhere else: if you feel like, you can go hunting for them :)

Have a look at the slackbuild.org templates - there's one for cmake

http://www.slackbuilds.org/templates/

Looks like an interesting little program, but they really need to work on some things still...
Writing the application log and configuration in the same directory as the binary is definitely not the way to go.
I tried to trick it with some scripting, but no success.

I compiled it on a VM quickly and it went well, although I got a few weird bugs which made it unusable. Very clean, simple interface though.

I created new issue in order to distribute package for Slackware on next release (issue #196)

About log and configuration file position, I agree is not good for an unix-like system. I will change that in next version (add of some binary parameters) (issue #197)

Let me know if you have already create your own Slackbuild :-)

yupz, it's here, but it's not yet usable for the reasons above ( if I can manifest a preference on where to save log and config, I would say $HOME/.silenteye/ ). :)
I also tried to guess the cmake options, if you have something better to suggest, it's welcomed ;)

Wow, looks like people have been way more proactive than I have. Sorry guys.

Since we're giving suggestions... :)

I'd say a system-wide configuration file should go to
/etc/<name_of_program>.conf
if only one file is needed, and
/etc/<name_of_program>/{xxx,yyy,zzz}
if several files are needed.

And "/etc/" actually should be configurable in the configure script (if using autotools) or with cmake.

User-specific configurations of course should go in $HOME/.<name_of_program>/

You can checkout pre-release code for version 0.4.2 of SilentEye, which include default path configuration for log and configuration, at :
see README_UNIX for cmake configuration and ./silenteye --help for command line options.

it needs cmake 2.8.5, we got 2.8.4 :(

ok, I cheated :p
http://ponce.cc/slackware/testing/silenteye/

but (dunno if the cheat above is involved) when I click on "Encode" it says: "Selected media doesn't have enough space to encode your message!", whatever destination folder I choose.
No related output on console, just
EDIT: tried a new checkout, revision 149: seems BMP encoding works, JPEG has the behaviour above (module is there and detected on configuration page), and switching formats made this appear on console
wav encoding and decoding works but alsa playback is not, "Audio device is not ready!" (no output on console).