CONTENTS DELETED
The author has deleted this message.
|
Le sam. 2 févr. 2019 à 07:02, Sambhav Dusad <[hidden email]> a écrit :
Hi, The GoSC 2019 projects will use the implementation available from digiKam "dplugins" git branch. This code will switch back to git master branch after digiKam 6.0.0 release, planed around the 10 february. So i recommend to checkout this branch and compile it. To compile all source code, you need to resolve all dependencies before. Check the list given in developers documentation : Installing all devel packages with headers and shared libraries is enough. If your Linux distro is well done, there is nothing to tune especially. Check well all dependency versions. When all is ready, run the bootstrap.linux script. If dependencies are missing cmake will report the problem on the console. When all is configured, it's time to compile. The script create a build sub-directory to separate compilation files from source files. Go to build and run the famous "make -jN", with N the number of CPU core to use. Here, with a i7 8 cores, 32 Gb of RAM, and a SSD storage, this take 10 minutes to compile from scratch. When all is compiled, form build sub-directory, run "make install/fast" to install whole digiKam in your system. Voilà, you will found more detail in online documentation if necessary. Best Gilles Caulier
|
CONTENTS DELETED
The author has deleted this message.
|
Le sam. 2 févr. 2019 à 21:10, Sambhav Dusad <[hidden email]> a écrit :
Not at all. KDE is not digiKam and vis versa. digiKAm is an application using some KF5 API. Install all devel package from digiKam dependencies list, configure digiKam source code with bootstrap script and compile. It's explained here : https://www.digikam.org/api/
use a good text editor as Kate (which can compile also with right module, after to configure from console), and recompile / install... Gilles |
Hi, Best Gilles Caulier Le sam. 2 févr. 2019 à 22:11, Gilles Caulier <[hidden email]> a écrit :
|
CONTENTS DELETED
The author has deleted this message.
|
Hi, You don't need to use download-repos script. All is already in place in fact. Just switch to the "dplugins" branch like this : git checkout -b dplugins remotes/origin/development/dplugins Now, you have a local dplugins branch following the remote one from the git server. "git branch -a" will give you the full list of branches (local and remote) "git pull" will be enough to update code in local, when code will change in remote server. Best Gilles Caulier Le lun. 4 févr. 2019 à 14:43, Sambhav Dusad <[hidden email]> a écrit :
|
CONTENTS DELETED
The author has deleted this message.
|
Le mar. 5 févr. 2019 à 06:14, Sambhav Dusad <[hidden email]> a écrit :
You can forget. This has nothing to do with the build workflow.
Wikipedia is always your friend : https://en.wikipedia.org/wiki/AppStream
yes. I cannot use it in my office due to FW limitation. I can use LinkedIn channel instead, or talking by mail if you prefer. Best Gilles Caulier |
CONTENTS DELETED
The author has deleted this message.
|
Ok, i see. It's strange because i cannot reproduce here under Linux and MacOS. I will disable this test code for the moment. Gilles Caulier Le mar. 5 févr. 2019 à 08:23, Sambhav Dusad <[hidden email]> a écrit : Thanks, I will look into the appstream more. |
Le mar. 5 févr. 2019 à 09:03, Gilles Caulier <[hidden email]> a écrit :
|
CONTENTS DELETED
The author has deleted this message.
|
Le mar. 5 févr. 2019 à 09:32, Sambhav Dusad <[hidden email]> a écrit : Thanks Gilles, Which one exactly ? For other contributors who try to build digiKam on Ubuntu, I found a decent Look the resize tools improvements to do : * For Batch Queue Management : Code location : https://cgit.kde.org/digikam.git/tree/core/dplugins/bqm/transform/resize?h=development/dplugins * For Image Editor : Code location : https://cgit.kde.org/digikam.git/tree/core/dplugins/editor/transform/resize?h=development/dplugins Both tools need to be homogeneous as possible. Please take a care to improve both at the same time. Read well the report and comment in bugzilla. Best Gilles Caulier |
CONTENTS DELETED
The author has deleted this message.
|
Le mar. 5 févr. 2019 à 16:09, Sambhav Dusad <[hidden email]> a écrit : I looked into the issues and tried reproducing them. Please correct me if I yes it is. > Currently, resize is limited to setting the desired length of one side of Better is to ask to bugzilla as well and share the Q with the end user. > The values should not be limited to 4000 pixels. Better use input boxes no need. the current slider widget is able to capture the value with right click. Again, please comment on bugzilla entry, it's better. Gilles Caulier |
CONTENTS DELETED
The author has deleted this message.
|
Le ven. 8 févr. 2019 à 09:07, Sambhav Dusad <[hidden email]> a écrit : Thanks, Gilles No, it's the right way. Note : if you touch only the plugin code, you just need to re-install the plugin. That all. So go to build/core/dplugins/.../_your_plugin_ and run make install/fast as root.
yes for the basis. But you are there to learn. The DK code base is already a good example and fully coded with Qt API (1.5 M code lines). Explore and ask in this room if necessary. I am comfortable in learning about it. So, please suggest me some tutorials Qt provide a package to install with all examples used in Qt API doc. it's a first start. Else look in Qt wiki forum, StackOverflow, Youtube, and the learn area from LinkedIn SN. Best Gilles Caulier |
Free forum by Nabble | Edit this page |