Registered Member
|
Yes, it seems the older scripts worked enough to DL the svn sources and begin the build process (which eventually failed), but this new one doesn't do much at all -- and I have no idea why either! What I've done, on my Kubuntu 7.10 machine: download the tarballed script that you recently posted, untar it, and copy it to /home/eljefe/_newfolder_/ This way, I start with a clean folder each time. open a command prompt at that location $ mkdir src build [i](if I don't do this I get a failure for sure)[/i] Pick the "Full" option; enter the full path for my source and build directories: Watch it skip the SVN downloads (SOMETIMES, but other times it seems to work??? like just now, it failed, then i wanted a better output for posting here, and it DID check out SVN... but the fail time I ran "./kdenlive_builder.sh > process.txt" and that file reads: $ cat process.txt and i don't know the reason it skipped, its almost certainly not due to the > redirect since it was doing that before also) Answer "Yes" to the three ffmpeg format options... watch it do its thing... AND OF COURSE the time I really *want* it to fail, its getting past my previous 53% always-fail point... And, great, it worked this time! I mean it, it is good news, but it doesn't help to fix my errors that I've been getting for days now... One thing I think we should consider is that, if the source and build directories don't exist, they should be created. Also, the variables should be cleared out (initialized?) at the beginning of running the various steps so that my build and source directory variables aren't held over from a previous run of the script (if my src dir doesn't exist i think it is checking SVN (when it works) into the one I had entered days ago, which sometimes doesn't exist and sometimes does and sometimes its been moved to KDE's trash). Well, I don't know. The build worked this time, but it doesn't run: eljefe@eljefe-desktop:~/try080214_10.30$ ./build/bin/kdenlive How can I point it to the correct libmlt++.so.0 file? I get the feeling it was looking at the system version in the past, which i recently removed... Thank you JM for your patience and help. I want to get it to run now, but I am at work so cannot look into the run error right now, maybe tonight (but its Valentines day, I may not have time tonight)... Thanks again!!!! |
Registered Member
|
OK yes i am at work but I want my KDEnlive! I read the post about linking to the correct libraries here and then I ran this: and started KDEnlive thus: eljefe@eljefe-desktop:~/try080214_10.30/build$ ./bin/kdenlive and KDEnlive came up (after specifying the correct path for MLT install as "/home/eljefe/try080214_10.30/build") and now I have it running! I am thrilled! and I cannot work on it until the weekend, likely! Oh well, we're up and running! How long does the "export LD_LIBRARY_PATH=/home/eljefe/try080214_10.30/build/lib/:$LD_LIBRARY_PATH" stay valid? Will that mess anything else up, or is that a KDEnlive-specific variable? |
Registered Member
|
Great :D I've just arrived home and going to have a look at the script when I saw your message ! Well, at the end it seems the script works !! Anyway, I'm trying to answer some of your questions just in case they are of help to anybody else: - In order to know if it needs to download sources, the script is looking for a "kdenlive" directory in your specified sources dir. If it does not find, then download a full version of the sources. If it finds, then only updates the sources (much quicker) but if svn find that you've already last version, then skip the process. Also, if for any reason you've an empty or non valid "kdenlive" directory in your sources dir, the script try to update sources but, as there's nothing to update, also skip. My suggestion is to create a sources dir in your home directory (or in /usr/src if you want to update main kdenlive installation) and use always the same directory. I can not find any reason to have multiple sources in the PC and this can be cause of some problems. - Yes, if the source and build directories do no exist, they are created and variables initialized. But be aware of what I mentioned before. I know that just checking existence of a directory is not a perfect way to check existence of all the source files, but really I do not know a better way. Any help appreciated ;) - Variable $LD_LIBRARY_PATH is a system variable to tell programs where to find necessary libs. If this variable does not point to the right directories, the program can not find libraries and fails (this is what you experienced). In theory, the script is prepared to automatically link the executable with the libraries, but as you've found this is not working and that's why it's necessary to setup the variable in the terminal before running kdenlive. I'm going to check in detail the script to try to find where the problem is, but I can not assure it will work. If succesful I'll post a new version. Well, let us know what you think about kdenlive when you'll be able to test it ! Hope it will delight you :) Regards. JM |
Registered Member
|
The updated scripts works for me. Thanks so much for fixing the script. It does find the correct svn mlt version without setting any library variables. |
Registered Member
|
I took a look at your script tonight and tried it out. On the ffmpeg configure options, you should remove --enable-pp, mlt does not use it at this time. Also, I would add --enable-pthreads to let SMP users take advantage of multi-threaded codecs. On the make commands, I suggest adding '-j2' to make it faster, even for non-SMP users. On the mlt configure step, I suggest --disable-mmx because mlt will fail on x86-64 systems without it. If you can detect the system type (e.g., 'file /bin/cat | grep x86-64' and get $?), then you can make it smart. Finally, LD_LIBRARY_PATH is more standard than LD_RUN_PATH and documented in 'man ld.so' I had to use LD_LIBRARY_PATH; LD_RUN_PATH did not work on my system. Users who do not install to /usr (and sometimes /usr/local) will not be able to run kdenlive without setting these env vars (PATH and LD_LIBRARY_PATH) each time they want to run kdenlive. You might consider generating a start_kdenlive script installed to DEST_DIR/bin to establish this environment and launch kdenlive. Or, rename kdenlive to kdenlive-bin and name the script kdenlive. Also, this launch script could detect if there is more than one CPU and set MLT_AVFORMAT_THREADS: CPUS=$(cat /proc/cpuinfo | grep processor | tail -1 | awk '{print $3}') |
Registered Member
|
Here is my launcher script: #!/bin/sh Of course, I can't really use the .desktop launcher, and I have to know to run $DEST_DIR/bin/kdenlive. |
Registered Member
|
Dan, thanks for your comments. I've included them in a new version of the script, again with some other improvements and I'm attaching here this new version. One of the improvements is to correct the use of LD_RUN_PATH, pointing to the right directory. If my behaviour is correct, this change will allow to dinamically link correct libraries with kdenlive executable at compilation time, so no need to set variable LD_LIBRARY_PATH when executing kdenlive. I've tested and seems to work ok for me, but appreciate if others can also test. (For those who doesn't know: Just execute the script, enter the terminal, go to the directory where you've installed the executables (xxx/bin) and execute kdenlive (./kdenlive). If my assumption is OK, you'll see a message telling that MLT has been found in your installation directory and not in /usr or /usr/local). Anyway, your execution script is still valid to set multithreads for MLT, so if you do not mind and depending on the result of previous test, I'll change and include also with the builder. Thanks again and best regards. *** EDITED *** Removed script as a new version has been posted in this thread |
Registered Member
|
Hi all,
Any ideas? I'm runny Ubuntu gutsy amd64, and have installed Cheers Deere. |
Registered Member
|
Hi, I'm attaching a new version of the script with following changes due modifications in ffmpeg structure: - Find correct avformat headers in in /libavformat (thanks to toohes for pointing this ;) ). Anyway, I think the right option is for Dan or JB to modify makefiles accordingly. Hope this helps. |
Registered Member
|
|
Registered Member
|
Hi, Cheers for the new script. Just dl'ed it and ran, it downloaded some updated versions, but is still failing to compile on mlt as below. Would it be something to do with my configuration?
deere wrote:
Hi all, |
Registered Member
|
deere wrote:
Hi all, Same here, I'm trying to look for -lsndfile EDIT: Fixed, after a quick search on packages.ubuntu.com, you have to install the package libsndfile1-dev |
Registered Member
|
>> you have to install the package libsndfile1-dev Thanks mridkash! Solved the problem. All good, success on Cheers. |
Registered Member
|
I try to build with the current script but i get problems linking kdenlive :( -- Check for working C compiler: /usr/bin/gcc I cannot figure out the problem. Can anybody help me? |
Registered Member
|
What distro are you using? With Debian-based distros (inc *buntus) I first added the multimedia repository (either Debian-Multimedia.org for Debian, or Medibuntu.org for *buntu); second I ran "apt-get build-dep mlt mlt++ kdenlive ffmpeg" as root, which installed needed packages for building the (old-but-available) versions of these apps; third I copied the new script from here:
Try that, or adapt to your distro, and let us know! |
Registered users: Bing [Bot], gfielding, Google [Bot], Sogou [Bot]