[kdenlive] [GSOC] Porting to Windows, need help with projetc details

[Klemen Ferjančič]

Unfortunately I missed the IRC meeting so I'll ask my last questions here.

I did a dependency check on existing package and found some extra libs. 
It's not the most current package but some of them were: dvgrab, freior, 
libiec, libgavl, dvdauthor... and more.

Are any of these required for the build or are they pluggable? I'm 
asking because I noticed with Kdenlive on Linux that some dependencies 
can be missing and it only affects the functionality but not the actual 
build. How does that work?


Dne 24.3.2015 ob 0:07 je Vincent Pinon zapisal(a):
> Le dimanche 22 mars 2015, 23:17:03 Mario Fux a écrit :
>> Am Sonntag, 22. März 2015, 18.08:28 schrieb Klemen Ferjančič:
>>> I've already been warned about the KF version situation. If I understand
>>> correctly, Kdenlive is currently on KF4 but is in the process of being
>>> ported to KF5? I guess it could be problematic if KF5 branch is not in
>>> stable enough state for me.
>>> Can someone explain me what is the current situation with Kdenlive and KF?
>> A KF5 based version of Kdenlive will be released as part of KDE Applications
>> 15.04 and thus in April and thus soon ;-). (damn, reminder to myself, should
>> start on release notes for 15.04 ;-).
> I confirm, branch "master" is about to be officially released ("Applications/15.04").
> Based on KF5, it should be usable (unfortunately not much tested), at least a good basis for work.
> The more unstable branch is "frameworks" in which JB and I are working on refactoring, still functional but not very safe...
>
>> In general KDE Frameworks 5 (KF5) or most of it should work on Windows too
>> (they're after all Qt Addons). And there is even work going on to extend our
>> KDE CI build infrastructure to Mac OSX and Windows. As I read tonight MacOSX
>> should already work.
> And it seems MacPorts are running quite well, as the bugs received from this platform don't seem blocking whole functionality.
>
>>> Are there any other dependencies which I should be worried about?
>> This is a question that Vincent and jb could answer.
> Kdenlive is based on MLT, itself based on FFmpeg.
> MLT is delivered on Mac and Windows at least for Shotcut (also based on Qt5).
>
> I don't expect much work on source are bringing dependences, those 2 ports are mainly a packaging work, for which we haven't much knowledge in the team...
>
>> Btw guys, what about a Kdenlive IRC meeting for all the GSoC interested
>> students?
> ==> https://framadate.org/ii781kpcyh98p31i
> (will remind in a separate mail)
>
>>>>> Specify exactly which tests I will carry out after successful build?
> Unfortunately we have not a single test written :-(
> I personally run small projects with several clip types, effects types (keyframe, region...), transitions, play with the opened timeline...
> really insufficient I admit.
>
>>>>> It is impossible to know what kind of problems could appear at
>>>>> compiling and linking so I'm not sure what to write on that. I am also
>>>>> not sure what exactly I should explain in regard to CI and installer
>>>>> since that's pretty much standardized stuff.
> Installer may be standard but we don't have it, don't find time/interest to learn and do it by ourselves...
> CI is on KDE sysadmins side, we should ask them (IRC?)
>
>>>>> Best regards, Klemen
> BR,
> Vincent
> _______________________________________________
> kdenlive mailing list
> kdenlive at kde.org
> https://mail.kde.org/mailman/listinfo/kdenlive
>