SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Search there for kdenlive, click in package name, then click in the right part where it says "Source Files"
and finally click in PKGBUILD (this is the Arch package build script).
Make your own slackbuild script using some template as I do for all my builds.
Also, take a look at how Arch Linux build the package you want:
Thanks, good idea. I usually fix available slackbuild script for newer versions with the guidance of arch's pkgbuild. I guess this building process for kdenlive in Slackware is so confusing that it will be easier to create a slackbuild script from scratch altogether.
In directory source/kde/kde/cmake, copy the default file 'cmake' to 'kdenlive' and edit it.
Ah! Nice, thanks!
I guess kdenlive is using some generic configure options, there are no specific file with instructions for it. I even tried find kde -iname "*kdenlive*" -type f but the files found are just mirrorlists, the slack-desc, a build checking flag for the script and the source files.
Ah! Nice, thanks!
I guess kdenlive is using some generic configure options, there are no specific file with instructions for it. I even tried find kde -iname "*kdenlive*" -type f but the files found are just mirrorlists, the slack-desc, a build checking flag for the script and the source files.
Yes, the file source/kde/kde/cmake/cmake is exactly the generic one which is used if there is not yet file source/kde/kde/cmake/kdenlive. That's why you need to copy source/kde/kde/cmake/cmake to source/kde/kde/cmake/kdenlive and edit it.
Yes, the file source/kde/kde/cmake/cmake is exactly the generic one which is used if there is not yet file source/kde/kde/cmake/kdenlive. That's why you need to copy source/kde/kde/cmake/cmake to source/kde/kde/cmake/kdenlive and edit it.
Sorry, I have misread the "to" with "and". I'll try that, thanks again.
I'm closing this since the main question was answered (how the rebuild, configure, etc kdenlive). Just a feedback: there is no special flag to set during compilation time for enabling features. Everything is detected at runtime, on startup. I've tried to recompile mlt, which is crucial for this detection apparently, but eventually I discovered that aac codec can be detected after clicking Menu Settings > Run Config Wizard. Tracking plugin won't work because it depends on OpenCV, but current ffmpeg is incompatible with current opencv, so you would have to downgrade it. Same thing for plugins which depends on lensfun, you'll have to recompile ffmpeg but against a newer lensfun than the current shipped.
So, I will have to stick to the official AppImage instead of the system version. Thanks everyone for the help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.