Re: Added some information about Qt Creator IDE integration to the wiki
On Fri, Feb 26, 2021 at 1:16 PM Michael Weghorn wrote: > On 26/02/2021 13.05, Hossein Noorikhah wrote: > > workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code > > project has all the .cxx and .h files. > > Looking at 'vs-code-template.code-workspace', it seems to just include > the whole source tree as a directory, so I suspect that there's no > problem since simply all header and source files in there will be included: Indeed - although relies on the compile-commands.json (vim-ide-integration) to associate/locate them for the code-completion (intellisense is configured to limit the completions to included files only), as the only fallback include paths defined in the workspace file are for the files included from unpacked external tarballs. Same for used defines to augment the editor display or the compile analysis. ciao Christian ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, You're right. Using .pro files for different directories is better than a single file. A single .pro file has problems caused from the overlap of include folders, in situations where things like this: #include and #include exist in two different files, in which the first "a" folder is different from the second "a", so that only one of these includes work. Performance can also be an issue. I cleaned up everything, built the project and re-generated the Qt Creator project files, and now everything seems to be fine. I am happy with the current qt integration, but I will try creating a per folder .pro files from all cxx/hxx files. Thanks, Hossein On Mon, Mar 1, 2021 at 11:50 AM Michael Weghorn wrote: > Hi, > > On 26/02/2021 16.02, Hossein Noorikhah wrote: > > On Fri, Feb 26, 2021 at 3:46 PM Michael Weghorn > wrote: > >> > >> > >> On 26/02/2021 13.05, Hossein Noorikhah wrote: > >>> workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code > >>> project has all the .cxx and .h files. > >> > >> Looking at 'vs-code-template.code-workspace', it seems to just include > >> the whole source tree as a directory, so I suspect that there's no > >> problem since simply all header and source files in there will be > included: > > > > So, why not do the same for the Qt Creator? It can cause no harm, since > > the build system is separate. Finding source files, adding them to a > single > > lo.pro file, and that's all. What do you think about such an approach? > > Maybe other useful file types can also be included. > > > > $ find -iname "*.cxx" -o -iname "*.hxx"|wc > >21243 21243 901070 > > Different modules can be built with different parameters (like defines, > include paths, compiler/linker flags), s.a. the .pro files. Mixing all > of them together and setting all of them for all source files wouldn't > really be "correct" in a strict sense. If I remember correctly, even > with the current approach, the flags for all libraries/executables in > one subdirectory are already "merged together". As long as there are no > conflicting options, this should be no problem in practice, though, and > *might* be no problem when doing everything it similarly in the > top-level lo.pro either. > > While those parameters in the .pro files are not relevant for the actual > build (since Qt Creator just calls 'make' anyway and that one does not > rely on what is set in the .pro files), Qt Creator uses the information > from the .pro files for its Clang Code Model, which provides e.g. > autocompletion, code navigation, displaying compiler warnings and errors. > > So I *guess* (but haven't tried) that just adding all the sources and > headers to lo.pro wouldn't give you a nice setup with the > '--enable-mergelibs' autogen option set either, since the code model > wouldn't work properly due to missing parameters (assuming that they are > not properly propagated to workdir/GbuildToJson, as it seems). > > > Conceptually, it would probably be "most correct" from a build system > perspective to have a separate .pro file for each library/executable > (e.g. to generate a single .pro file for each of the > 'workdir/GbuildToJson/Library/libvclplug_*' files instead of merging > them into 'vcl/vcl.pro'). > > > However, I'd say it makes sense to be pragmatic, so IMHO, it's a > question of what the practical advantages/disadvantages of changing the > current approach would be. > Since the current approach is working fine for me (and it has been like > that since I've been using it; I'm not the original author of > qtcreator-ide-integration), I didn't see a real "need" to further > evaluate changing the way of how this aspect is handled so far. > If there are practical advantages of changing that (to either just have > a single top-level .pro file or further split the current ones), I see > no reason not to do so. > > Two more thoughts on the current handling came to my mind: > > 1) You can also just build a single module by e.g. right-clicking on the > "vcl" directory in Qt Creator and selecting "build vcl".). It's also > possible to just load e.g. vcl.pro as a project instead of the whole > lo.pro. I've never really used that myself, since loading the full > project is reasonably fast and I build from command line most times > anyway, but it might be something to keep in mind when evaluating what > pros/cons different approaches have. > > 2) With the current approach, you just see those source files in the > project view that are actually compiled (e.g. don't see Windows-specific > files when building on Linux). That can be seen as either an advantage > or a disadvantage. > > > Regards, > Michael > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, On 26/02/2021 16.02, Hossein Noorikhah wrote: On Fri, Feb 26, 2021 at 3:46 PM Michael Weghorn wrote: On 26/02/2021 13.05, Hossein Noorikhah wrote: workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code project has all the .cxx and .h files. Looking at 'vs-code-template.code-workspace', it seems to just include the whole source tree as a directory, so I suspect that there's no problem since simply all header and source files in there will be included: So, why not do the same for the Qt Creator? It can cause no harm, since the build system is separate. Finding source files, adding them to a single lo.pro file, and that's all. What do you think about such an approach? Maybe other useful file types can also be included. $ find -iname "*.cxx" -o -iname "*.hxx"|wc 21243 21243 901070 Different modules can be built with different parameters (like defines, include paths, compiler/linker flags), s.a. the .pro files. Mixing all of them together and setting all of them for all source files wouldn't really be "correct" in a strict sense. If I remember correctly, even with the current approach, the flags for all libraries/executables in one subdirectory are already "merged together". As long as there are no conflicting options, this should be no problem in practice, though, and *might* be no problem when doing everything it similarly in the top-level lo.pro either. While those parameters in the .pro files are not relevant for the actual build (since Qt Creator just calls 'make' anyway and that one does not rely on what is set in the .pro files), Qt Creator uses the information from the .pro files for its Clang Code Model, which provides e.g. autocompletion, code navigation, displaying compiler warnings and errors. So I *guess* (but haven't tried) that just adding all the sources and headers to lo.pro wouldn't give you a nice setup with the '--enable-mergelibs' autogen option set either, since the code model wouldn't work properly due to missing parameters (assuming that they are not properly propagated to workdir/GbuildToJson, as it seems). Conceptually, it would probably be "most correct" from a build system perspective to have a separate .pro file for each library/executable (e.g. to generate a single .pro file for each of the 'workdir/GbuildToJson/Library/libvclplug_*' files instead of merging them into 'vcl/vcl.pro'). However, I'd say it makes sense to be pragmatic, so IMHO, it's a question of what the practical advantages/disadvantages of changing the current approach would be. Since the current approach is working fine for me (and it has been like that since I've been using it; I'm not the original author of qtcreator-ide-integration), I didn't see a real "need" to further evaluate changing the way of how this aspect is handled so far. If there are practical advantages of changing that (to either just have a single top-level .pro file or further split the current ones), I see no reason not to do so. Two more thoughts on the current handling came to my mind: 1) You can also just build a single module by e.g. right-clicking on the "vcl" directory in Qt Creator and selecting "build vcl".). It's also possible to just load e.g. vcl.pro as a project instead of the whole lo.pro. I've never really used that myself, since loading the full project is reasonably fast and I build from command line most times anyway, but it might be something to keep in mind when evaluating what pros/cons different approaches have. 2) With the current approach, you just see those source files in the project view that are actually compiled (e.g. don't see Windows-specific files when building on Linux). That can be seen as either an advantage or a disadvantage. Regards, Michael ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, On Fri, Feb 26, 2021 at 3:34 PM Michael Weghorn wrote: > In a previous email, you had mentioned: > > > I had issues with other IDE integration outputs which need separate > > discussions. > > I'm wondering whether those might all have the same root cause. > > In any case, can you try again using e.g. the build params I had > mentioned earlier or those recommended in the wiki for development to > see whether that works for you as well? > It's probably best to run 'git clean -dxf' first for a fresh start. I could have cleaned the "core" folder, but I decided to remove it all, and clone again. I am using the exact same "autogen.input" you have provided, and now I am waiting for a complete rebuild. On Fri, Feb 26, 2021 at 3:46 PM Michael Weghorn wrote: > > > On 26/02/2021 13.05, Hossein Noorikhah wrote: > > workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code > > project has all the .cxx and .h files. > > Looking at 'vs-code-template.code-workspace', it seems to just include > the whole source tree as a directory, so I suspect that there's no > problem since simply all header and source files in there will be included: So, why not do the same for the Qt Creator? It can cause no harm, since the build system is separate. Finding source files, adding them to a single lo.pro file, and that's all. What do you think about such an approach? Maybe other useful file types can also be included. $ find -iname "*.cxx" -o -iname "*.hxx"|wc 21243 21243 901070 Regards, Hossein ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 26/02/2021 13.05, Hossein Noorikhah wrote:
workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code
project has all the .cxx and .h files.
Looking at 'vs-code-template.code-workspace', it seems to just include
the whole source tree as a directory, so I suspect that there's no
problem since simply all header and source files in there will be included:
...
"folders": [
{
"name": "srcdir",
"path": "/home/michi/development/git/libreoffice"
},
It's weird that it tries to create a 'core/core.pro' and
'core/core.pro.shared', I don't have any such files here.
Is it correct that directory
'/home/hossein/Projects/libreoffice/core/core/' does not exist?
No, I don't have any directory named core/core.
I'm going to remove the whole source directory and try building again.
See my other mail from just now, this should hopefully work with
different autogen options.
Regards,
Michael
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, > qtcreator-ide-integration (and the other IDE integrations as well) uses > information from gbuild (the LO build system). > Does 'workdir/GbuildToJson/Library/libvcllo.so' have an entry > 'source/window/menu'? > > You can check e.g. by using > > grep -E --color 'source/window/menu( |$)' > workdir/GbuildToJson/Library/libvcllo.so > workdir/GbuildToJson/Library/libvcllo.so is blank. But VS Code project has all the .cxx and .h files. > It's weird that it tries to create a 'core/core.pro' and > 'core/core.pro.shared', I don't have any such files here. > Is it correct that directory > '/home/hossein/Projects/libreoffice/core/core/' does not exist? No, I don't have any directory named core/core. I'm going to remove the whole source directory and try building again. Regards, Hossein On Fri, Feb 26, 2021 at 1:57 PM Michael Weghorn wrote: > > On 26/02/2021 10.33, Hossein Noorikhah wrote: > > I am using the latest Ubuntu LTS. > > There is no autogen.input here, I usually run ./autogen.sh without any > > parameters, but I have this in autogen.lastrun: > > > > ./autogen.sh --with-distro=LibreOfficeLinux > > > > Although I think the last run of autogen.sh was without any parameters. > > If run without any parameters, './autogen.sh' will use the params set in > 'autogen.input', and if that's not present, those from > 'autogen.lastrun', so that's OK. > > My current autogen.input contains these params: > > --enable-ccache > --enable-dbgutil > --enable-werror > --enable-gtk3-kde5 > --enable-qt5 > --enable-kf5 > --without-doxygen > --with-jdk-home=/usr/lib/jvm/java-11-openjdk-amd64/ > --enable-python=fully-internal > --with-valgrind > --enable-split-debug > --enable-ld=gold > --enable-gdb-index > --enable-online-update > > Not sure whether it's related to the qtcreator issue we're discussing, > but in case you should want to debug LO, you'll probably want > '--enable-debug' or '--enable-dbgutil'. > > > > > The vcl.pro file is also attached. Look at these results: > > > > hossein@linux:~/Projects/libreoffice/core/vcl$ find -iname "*.cxx"|wc > > 830 830 26203 > > hossein@linux:~/Projects/libreoffice/core/vcl$ find -iname "*.hxx"|wc > > 388 388 10798 > > hossein@linux:~/Projects/libreoffice/core/vcl$ wc vcl.pro > >816 1631 56830 vcl.pro > > hossein@linux:~/Projects/libreoffice/core/vcl$ grep .cxx vcl.pro | wc > > 202 405 15719 > > hossein@linux:~/Projects/libreoffice/core/vcl$ grep .hxx vcl.pro | wc > > 294 589 20919 > > > > A lot of files are missing in the vcl.pro > > qtcreator-ide-integration (and the other IDE integrations as well) uses > information from gbuild (the LO build system). > Does 'workdir/GbuildToJson/Library/libvcllo.so' have an entry > 'source/window/menu'? > > You can check e.g. by using > > grep -E --color 'source/window/menu( |$)' > workdir/GbuildToJson/Library/libvcllo.so ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 26/02/2021 11.32, Michael Weghorn wrote: Please note that I have cloned LibreOffice core in the ~/Projects/libreoffice folder, and then built it. sudo apt-get build-dep libreoffice cd ~/Projects/libreoffice git clone git://anongit.freedesktop.org/libreoffice/core cd core ./autogen.sh make I'll try that here to see how it behaves for me when I take those steps, then run 'make qtcreator-ide-integration'. Can you possibly send me your 'workdir/GbuildToJson/' so I can see whether there's anything obviously weird in there? I can't reproduce by using exactly those steps, i.e. mkdir -p ~/Projects/libreoffice cd ~/Projects/libreoffice/ git clone git://anongit.freedesktop.org/libreoffice/core cd core/ ./autogen.sh make make qtcreator-ide-integration grep -E --color 'source/window/menu( |$)' workdir/GbuildToJson/Library/libvcllo.so worked fine for me, but I can reproduce with the '--with-distro=LibreOfficeLinux' param you mentioned in your other email, i.e. running this afterwards: git clean -dxf ./autogen.sh --with-distro=LibreOfficeLinux make make qtcreator-ide-integration I get the $ make qtcreator-ide-integration make -j 64 -rs -f /home/michael.weghorn/Projects/libreoffice/core/Makefile.gbuild gbuildtojson cd /home/michael.weghorn/Projects/libreoffice/core && /home/michael.weghorn/Projects/libreoffice/core/bin/gbuild-to-ide --ide qtcreator --make make ERROR : creating pro file=/home/michael.weghorn/Projects/libreoffice/core/core/core.pro [Errno 2] No such file or directory: '/home/michael.weghorn/Projects/libreoffice/core/core/core.pro' Traceback (most recent call last): File "/home/michael.weghorn/Projects/libreoffice/core/bin/gbuild-to-ide", line 1773, in emit with open(qt_pro_file, mode) as fpro: FileNotFoundError: [Errno 2] No such file or directory: '/home/michael.weghorn/Projects/libreoffice/core/core/core.pro' ERROR : creating pro.shared file=/home/michael.weghorn/Projects/libreoffice/core/core/core.pro.shared [Errno 2] No such file or directory: '/home/michael.weghorn/Projects/libreoffice/core/core/core.pro.shared' Traceback (most recent call last): File "/home/michael.weghorn/Projects/libreoffice/core/bin/gbuild-to-ide", line 1787, in emit with open(qt_pro_shared_file, mode) as fproshared: FileNotFoundError: [Errno 2] No such file or directory: '/home/michael.weghorn/Projects/libreoffice/core/core/core.pro.shared' Successfully created the project files. as well and $ grep -E --color 'source/window/menu( |$)' workdir/GbuildToJson/Library/libvcllo.so grep: workdir/GbuildToJson/Library/libvcllo.so: No such file or directory and grep -r source/window/menu workdir/GbuildToJson/ does not show any hit at all, so it seems that gbuild does not generate the relevant information when the '--with-distro=LibreOfficeLinux' param is used (and all the qtcreator-related issues are probably just a consequence of this). You could check the single params set in 'distro-configs/LibreOfficeLinux.conf' to see which one is the "problematic" one. At a quick glance, '--enable-mergelibs' looks like it might be related. In a previous email, you had mentioned: I had issues with other IDE integration outputs which need separate discussions. I'm wondering whether those might all have the same root cause. In any case, can you try again using e.g. the build params I had mentioned earlier or those recommended in the wiki for development to see whether that works for you as well? It's probably best to run 'git clean -dxf' first for a fresh start. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 26/02/2021 10.06, Hossein Noorikhah wrote: I am using the latest git master, and here is the result of the command. The same error is shown when I set the paths and run "gbuild-to-ide" manually. - hossein@linux:~/Projects/libreoffice/core$ make qtcreator-ide-integration make -j 8 -rs -f /home/hossein/Projects/libreoffice/core/Makefile.gbuild gbuildtojson cd /home/hossein/Projects/libreoffice/core && /home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide --ide qtcreator --make make ERROR : creating pro file=/home/hossein/Projects/libreoffice/core/core/core.pro [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro' Traceback (most recent call last): File "/home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide", line 1773, in emit with open(qt_pro_file, mode) as fpro: FileNotFoundError: [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro' ERROR : creating pro.shared file=/home/hossein/Projects/libreoffice/core/core/core.pro.shared [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro.shared' Traceback (most recent call last): File "/home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide", line 1787, in emit with open(qt_pro_shared_file, mode) as fproshared: FileNotFoundError: [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro.shared' It's weird that it tries to create a 'core/core.pro' and 'core/core.pro.shared', I don't have any such files here. Is it correct that directory '/home/hossein/Projects/libreoffice/core/core/' does not exist? (which would explain the error messages when trying to create the files, but not why this is attempted at all...). Please note that I have cloned LibreOffice core in the ~/Projects/libreoffice folder, and then built it. sudo apt-get build-dep libreoffice cd ~/Projects/libreoffice git clone git://anongit.freedesktop.org/libreoffice/core cd core ./autogen.sh make I'll try that here to see how it behaves for me when I take those steps, then run 'make qtcreator-ide-integration'. Can you possibly send me your 'workdir/GbuildToJson/' so I can see whether there's anything obviously weird in there? ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 26/02/2021 10.33, Hossein Noorikhah wrote: I am using the latest Ubuntu LTS. There is no autogen.input here, I usually run ./autogen.sh without any parameters, but I have this in autogen.lastrun: ./autogen.sh --with-distro=LibreOfficeLinux Although I think the last run of autogen.sh was without any parameters. If run without any parameters, './autogen.sh' will use the params set in 'autogen.input', and if that's not present, those from 'autogen.lastrun', so that's OK. My current autogen.input contains these params: --enable-ccache --enable-dbgutil --enable-werror --enable-gtk3-kde5 --enable-qt5 --enable-kf5 --without-doxygen --with-jdk-home=/usr/lib/jvm/java-11-openjdk-amd64/ --enable-python=fully-internal --with-valgrind --enable-split-debug --enable-ld=gold --enable-gdb-index --enable-online-update Not sure whether it's related to the qtcreator issue we're discussing, but in case you should want to debug LO, you'll probably want '--enable-debug' or '--enable-dbgutil'. The vcl.pro file is also attached. Look at these results: hossein@linux:~/Projects/libreoffice/core/vcl$ find -iname "*.cxx"|wc 830 830 26203 hossein@linux:~/Projects/libreoffice/core/vcl$ find -iname "*.hxx"|wc 388 388 10798 hossein@linux:~/Projects/libreoffice/core/vcl$ wc vcl.pro 816 1631 56830 vcl.pro hossein@linux:~/Projects/libreoffice/core/vcl$ grep .cxx vcl.pro | wc 202 405 15719 hossein@linux:~/Projects/libreoffice/core/vcl$ grep .hxx vcl.pro | wc 294 589 20919 A lot of files are missing in the vcl.pro qtcreator-ide-integration (and the other IDE integrations as well) uses information from gbuild (the LO build system). Does 'workdir/GbuildToJson/Library/libvcllo.so' have an entry 'source/window/menu'? You can check e.g. by using grep -E --color 'source/window/menu( |$)' workdir/GbuildToJson/Library/libvcllo.so ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, I am using the latest git master, and here is the result of the command. The same error is shown when I set the paths and run "gbuild-to-ide" manually. - hossein@linux:~/Projects/libreoffice/core$ make qtcreator-ide-integration make -j 8 -rs -f /home/hossein/Projects/libreoffice/core/Makefile.gbuild gbuildtojson cd /home/hossein/Projects/libreoffice/core && /home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide --ide qtcreator --make make ERROR : creating pro file=/home/hossein/Projects/libreoffice/core/core/core.pro [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro' Traceback (most recent call last): File "/home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide", line 1773, in emit with open(qt_pro_file, mode) as fpro: FileNotFoundError: [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro' ERROR : creating pro.shared file=/home/hossein/Projects/libreoffice/core/core/core.pro.shared [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro.shared' Traceback (most recent call last): File "/home/hossein/Projects/libreoffice/core/bin/gbuild-to-ide", line 1787, in emit with open(qt_pro_shared_file, mode) as fproshared: FileNotFoundError: [Errno 2] No such file or directory: '/home/hossein/Projects/libreoffice/core/core/core.pro.shared' Successfully created the project files. - Please note that I have cloned LibreOffice core in the ~/Projects/libreoffice folder, and then built it. sudo apt-get build-dep libreoffice cd ~/Projects/libreoffice git clone git://anongit.freedesktop.org/libreoffice/core cd core ./autogen.sh make Regards, Hossein On Fri, Feb 26, 2021 at 11:28 AM Michael Weghorn wrote: > > > On 26/02/2021 08.53, Michael Weghorn wrote: > > This is on Debian testing and I've checked that on Windows as well. > > Can you share your autogen.input (if present) and share your vcl.pro via > > pastebin (or send by email)? > > Now that the Jenkins CI builds have finished, I have merged the pending > patches. It may be worth trying again with current master first, in case > any of the changes might already have fixed the issue for your setup... ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 26/02/2021 08.53, Michael Weghorn wrote: This is on Debian testing and I've checked that on Windows as well. Can you share your autogen.input (if present) and share your vcl.pro via pastebin (or send by email)? Now that the Jenkins CI builds have finished, I have merged the pending patches. It may be worth trying again with current master first, in case any of the changes might already have fixed the issue for your setup... ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi Hossein, On 26/02/2021 07.46, Hossein Noorikhah wrote: Not all sources are included in the project. Look at vcl/source/window/menu.cxx https://opengrok.libreoffice.org/xref/core/vcl/source/window/menu.cxx I can not find this file in vcl.pro or any other .pro file. Is it intentional? That should be present, and it is in my case: $ grep 'source/window/menu.cxx' -- vcl/vcl.pro /home/michi/development/git/libreoffice/vcl/source/window/menu.cxx \ The above is the output with the pending changes in Gerrit in place already (so that absolute paths are used), but I see the entry (with path relative to the vcl/ directory) in the files I had uploaded earlier as well [1]: $ tar xf qtc_autogenerated.tar.gz $ grep 'source/window/menu.cxx' vcl/vcl.pro source/window/menu.cxx \ This is on Debian testing and I've checked that on Windows as well. Can you share your autogen.input (if present) and share your vcl.pro via pastebin (or send by email)? Regards, Michael [1] https://nextcloud.documentfoundation.org/s/cXTdxJPw83cfTd3 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi Hossein, On 25/02/2021 18.10, Hossein Noorikhah wrote: Now I am using the latest LibreOffice master build which uses .pro.shared files. Everything works just fine, except that 'Replacement for "Desktop"' Qt kit, which does not cause harm to the build process. If this is unavoidable at this point, I am ok with it. I currently don't see a good way to avoid this while still having proper run and build configurations, since this is how Qt Creator's handling of kits works: If no existing kit is set, it creates such a new "Replacement" kit to take over settings, s. Qt Creator's source code: https://codereview.qt-project.org/gitweb?p=qt-creator/qt-creator.git;a=blob_plain;f=src/plugins/projectexplorer/project.cpp;hb=caaad2107db4f6c1150d40d8d6c01eb6b21bede1 - method 'Project::createTargetFromMap'. I see these build configurations: 01-Global Build 02-Global tests -- quick tests (unitcheck) 03-Global tests -- slow tests (unitcheck, slowcheck, screenshot) 04-Global tests -- integration tests (unitcheck, slowcheck, screenshot, subsequentcheck) 05-Global tests -- performance tests (perfcheck) 06-Global tests -- tests (check) 07-Global build -- nocheck 08-Global build -- build-l10n-only 09-Global build -- build-non-l10n-only 10-Global build -- clean 11-Global build -- clean-build 12-Global build -- clean-host with the run settings as expected, having the correct executable and path in place. Great. I try to update the wiki entry "Development/IDE" according to your changes, and I appreciate your help in adding any relevant information. Thanks! Please just go ahead, I think you'll probably best know what information is helpful for someone who starts "from scratch". :-) I'll be happy to review that in the end. However, let's first try to identify the other remaining issue in your setup, I'll reply to your other email in a moment. Regards, Michael ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi Michael,
Not all sources are included in the project. Look at vcl/source/window/menu.cxx
https://opengrok.libreoffice.org/xref/core/vcl/source/window/menu.cxx
I can not find this file in vcl.pro or any other .pro file. Is it intentional?
Regards,
Hossein
On Thu, Feb 25, 2021 at 8:40 PM Hossein Noorikhah wrote:
>
> Hi Michael,
>
> Thank you for spending time to improve Qt Creator IDE support.
>
> Now I am using the latest LibreOffice master build which uses .pro.shared
> files.
> Everything works just fine, except that 'Replacement for "Desktop"' Qt kit,
> which does not cause harm to the build process. If this is unavoidable at this
> point, I am ok with it.
>
> I see these build configurations:
>
> 01-Global Build
> 02-Global tests -- quick tests (unitcheck)
> 03-Global tests -- slow tests (unitcheck, slowcheck, screenshot)
> 04-Global tests -- integration tests (unitcheck, slowcheck, screenshot,
> subsequentcheck)
> 05-Global tests -- performance tests (perfcheck)
> 06-Global tests -- tests (check)
> 07-Global build -- nocheck
> 08-Global build -- build-l10n-only
> 09-Global build -- build-non-l10n-only
> 10-Global build -- clean
> 11-Global build -- clean-build
> 12-Global build -- clean-host
>
> with the run settings as expected, having the correct executable and path in
> place.
>
> And, I am not using a separate build dir, but I thank you for adding support
> for
> that build configuration.
>
> I try to update the wiki entry "Development/IDE" according to your changes,
> and
> I appreciate your help in adding any relevant information.
>
> Regards,
> Hossein
>
>
> On Thu, Feb 25, 2021 at 5:58 PM Michael Weghorn wrote:
> >
> >
> > On 15/02/2021 12.26, Michael Weghorn wrote:
> > > In order to directly match an actual kit, one could try to retrieve the
> > > UUID for a valid kit from the settings in the Qt Creator profile and use
> > > that one when generating the *.pro.user files, but that's not ideal
> > > either in my opinion (e.g. one would have to "guess" what kit is the
> > > right one, rely on a specific Qt Creator profile path,...).
> > >
> > > I just recently read about *.pro.shared files [1] which are actually
> > > meant to share project settings. Those might actually be a better way to
> > > handle all of this.
> > > I'll probably take a closer look at some point in time.
> >
> > From commit e827cb144ee9886134a946c7a3b316f9eeb83168 ("qtcreator:
> > Create *.pro.shared files instead of *.pro.user") on, *.pro.shared files
> > will be generated.
> > If you still don't want to use the autogenerated and autoselected kit
> > with build/run settings, this will at least make sure you don't have to
> > configure your custom settings every time, since the *.pro.user file
> > holding the settings is no longer overwritten every time that
> > 'make qtcreator-ide-integration' is run.
> >
> > >> And for the contents of lo.pro, I still get "." as the first
> > >> subdirectory. I have to
> > >> manually change it to "../core".
> > >
> > > As mentioned in my previous email, I can take a quick look whether I can
> > > see anything obvious if you upload your generated files somewhere or
> > > send them by email and tell me the paths used in your case (and whether
> > > you use a separate build dir).
> >
> > I've seen a similar error message to yours when testing with a separate
> > build dir that is not on the same "hierarchy level" in the file system
> > as the source dir (srcdir: ~/development/git/libreoffice, builddir:
> > ~/temp/lobuild):
> >
> > ~/development/git/libreoffice/lo.pro:-1: error: Could not find .pro
> > file for subdirectory "../../development/git/libreoffice/UnoControls" in
> > "~/development/git/libreoffice/../../development/git/libreoffice/UnoControls".
> >
> > Pending Gerrit change [1] ("qtcreator: Create *.pro and *.pro.shared
> > files in builddir, not srcdir") (and its ancestors) should fix cases
> > where builddir != srcdir, hopefully fixing your problem as well (for
> > which I don't know the details, so can't explicitly test that).
> >
> > I'll update the wiki entry [2] later, once everything has been merged.
> >
> >
> > [1] https://gerrit.libreoffice.org/c/core/+/111553
> > [2] https://wiki.documentfoundation.org/Development/IDE#Qt_Creator
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi Michael,
Thank you for spending time to improve Qt Creator IDE support.
Now I am using the latest LibreOffice master build which uses .pro.shared files.
Everything works just fine, except that 'Replacement for "Desktop"' Qt kit,
which does not cause harm to the build process. If this is unavoidable at this
point, I am ok with it.
I see these build configurations:
01-Global Build
02-Global tests -- quick tests (unitcheck)
03-Global tests -- slow tests (unitcheck, slowcheck, screenshot)
04-Global tests -- integration tests (unitcheck, slowcheck, screenshot,
subsequentcheck)
05-Global tests -- performance tests (perfcheck)
06-Global tests -- tests (check)
07-Global build -- nocheck
08-Global build -- build-l10n-only
09-Global build -- build-non-l10n-only
10-Global build -- clean
11-Global build -- clean-build
12-Global build -- clean-host
with the run settings as expected, having the correct executable and path in
place.
And, I am not using a separate build dir, but I thank you for adding support for
that build configuration.
I try to update the wiki entry "Development/IDE" according to your changes, and
I appreciate your help in adding any relevant information.
Regards,
Hossein
On Thu, Feb 25, 2021 at 5:58 PM Michael Weghorn wrote:
>
>
> On 15/02/2021 12.26, Michael Weghorn wrote:
> > In order to directly match an actual kit, one could try to retrieve the
> > UUID for a valid kit from the settings in the Qt Creator profile and use
> > that one when generating the *.pro.user files, but that's not ideal
> > either in my opinion (e.g. one would have to "guess" what kit is the
> > right one, rely on a specific Qt Creator profile path,...).
> >
> > I just recently read about *.pro.shared files [1] which are actually
> > meant to share project settings. Those might actually be a better way to
> > handle all of this.
> > I'll probably take a closer look at some point in time.
>
> From commit e827cb144ee9886134a946c7a3b316f9eeb83168 ("qtcreator:
> Create *.pro.shared files instead of *.pro.user") on, *.pro.shared files
> will be generated.
> If you still don't want to use the autogenerated and autoselected kit
> with build/run settings, this will at least make sure you don't have to
> configure your custom settings every time, since the *.pro.user file
> holding the settings is no longer overwritten every time that
> 'make qtcreator-ide-integration' is run.
>
> >> And for the contents of lo.pro, I still get "." as the first
> >> subdirectory. I have to
> >> manually change it to "../core".
> >
> > As mentioned in my previous email, I can take a quick look whether I can
> > see anything obvious if you upload your generated files somewhere or
> > send them by email and tell me the paths used in your case (and whether
> > you use a separate build dir).
>
> I've seen a similar error message to yours when testing with a separate
> build dir that is not on the same "hierarchy level" in the file system
> as the source dir (srcdir: ~/development/git/libreoffice, builddir:
> ~/temp/lobuild):
>
> ~/development/git/libreoffice/lo.pro:-1: error: Could not find .pro
> file for subdirectory "../../development/git/libreoffice/UnoControls" in
> "~/development/git/libreoffice/../../development/git/libreoffice/UnoControls".
>
> Pending Gerrit change [1] ("qtcreator: Create *.pro and *.pro.shared
> files in builddir, not srcdir") (and its ancestors) should fix cases
> where builddir != srcdir, hopefully fixing your problem as well (for
> which I don't know the details, so can't explicitly test that).
>
> I'll update the wiki entry [2] later, once everything has been merged.
>
>
> [1] https://gerrit.libreoffice.org/c/core/+/111553
> [2] https://wiki.documentfoundation.org/Development/IDE#Qt_Creator
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 15/02/2021 12.26, Michael Weghorn wrote:
In order to directly match an actual kit, one could try to retrieve the
UUID for a valid kit from the settings in the Qt Creator profile and use
that one when generating the *.pro.user files, but that's not ideal
either in my opinion (e.g. one would have to "guess" what kit is the
right one, rely on a specific Qt Creator profile path,...).
I just recently read about *.pro.shared files [1] which are actually
meant to share project settings. Those might actually be a better way to
handle all of this.
I'll probably take a closer look at some point in time.
From commit e827cb144ee9886134a946c7a3b316f9eeb83168 ("qtcreator:
Create *.pro.shared files instead of *.pro.user") on, *.pro.shared files
will be generated.
If you still don't want to use the autogenerated and autoselected kit
with build/run settings, this will at least make sure you don't have to
configure your custom settings every time, since the *.pro.user file
holding the settings is no longer overwritten every time that
'make qtcreator-ide-integration' is run.
And for the contents of lo.pro, I still get "." as the first
subdirectory. I have to
manually change it to "../core".
As mentioned in my previous email, I can take a quick look whether I can
see anything obvious if you upload your generated files somewhere or
send them by email and tell me the paths used in your case (and whether
you use a separate build dir).
I've seen a similar error message to yours when testing with a separate
build dir that is not on the same "hierarchy level" in the file system
as the source dir (srcdir: ~/development/git/libreoffice, builddir:
~/temp/lobuild):
~/development/git/libreoffice/lo.pro:-1: error: Could not find .pro
file for subdirectory "../../development/git/libreoffice/UnoControls" in
"~/development/git/libreoffice/../../development/git/libreoffice/UnoControls".
Pending Gerrit change [1] ("qtcreator: Create *.pro and *.pro.shared
files in builddir, not srcdir") (and its ancestors) should fix cases
where builddir != srcdir, hopefully fixing your problem as well (for
which I don't know the details, so can't explicitly test that).
I'll update the wiki entry [2] later, once everything has been merged.
[1] https://gerrit.libreoffice.org/c/core/+/111553
[2] https://wiki.documentfoundation.org/Development/IDE#Qt_Creator
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, On 12/02/2021 21.53, Hossein Noorikhah wrote: I went through the sequence, and nothing has changed. It's a question for me: why do we need a fresh Qt Creator profile? In very rare situations, I had to clean up this profile. Also, I usually do not re-run ./autogen.sh because I didn't have any changes in the libs/configurations, and I only pulled the latest master from the git repository. This time, I re-ran autogen.sh again, and again nothing has changed. There's generally no need for a fresh Qt Creator profile. I just did that to avoid potential side-effects of an existing profile when double-checking it works for me. There shouldn't be any need to manually re-run autogen.sh either unless you change your autogen.input. But, now I know what you're doing. I thought that only lo.pro is generated, but now I see that lo.pro.user is also being generated. That didn't help me, because the used Qt kit was not ok. I saw a manual Qt kit which is used for the configuration. It was called 'Replacement for "Desktop"', so I removed it and reconfigured the project using the appropriate kit. In this case, I had to add the previously discussed configurations manually. Can you try what happens if you use that 'Replacement for "Desktop"' kit instead? That's what I'm doing and which should contain the settings from lo.pro.user (i.e. the build and run configurations). As far as I can see, the *.pro.user contains settings specific to one kit, and those kits have unique UUIDs, i.e. are different for each user/profile, which is why that can't be mapped to your existing kit. To create a viable solution that lasts even when you re-configure the project, I think it is needed to put all the configuration in .pro files, and not in .pro.user files, because they can be removed/changed at any time. I'd generally agree, but currently don't see a way to make this work. *.pro files are not files for the Qt Creator IDE in the first place, but for the qmake build system (which is one of the build systems that Qt Creator supports). The *.pro.user file is used to store user-specific Qt-Creator-specific settings for a project. When loading a qmake project (using the .pro file) in Qt Creator, it tries to automatically derive the corresponding build and run settings, which is also why you get the "qmake" build step etc. if you just use the *.pro file and not the *.pro.user one. That's why the *pro.user file is used to set "proper" build steps and run configuration for the LO case. I currently see no way to instead derive those automatically from the .pro file only. In other words: The current way that qtcreator IDE integration works is by generating a fake qmake project (using .pro files) for LibreOffice, then manually overriding run/build configurations using the .pro.user files. This is necessary because LO actually uses its own build system (gbuild), for which there is no native support in Qt Creator. That's a bit of a hack; things would probably be a bit easier if LO wasn't using its own build system but one of those natively supported by Qt Creator (like CMake, qmake or meson (for which there is experimental support)). Generating the *.pro.user files is actually not ideal and they're not really meant to be shared, but it seems to be working well for me in practice when I select the 'Replacement for "Desktop"' kit when initially loading the project. In order to directly match an actual kit, one could try to retrieve the UUID for a valid kit from the settings in the Qt Creator profile and use that one when generating the *.pro.user files, but that's not ideal either in my opinion (e.g. one would have to "guess" what kit is the right one, rely on a specific Qt Creator profile path,...). I just recently read about *.pro.shared files [1] which are actually meant to share project settings. Those might actually be a better way to handle all of this. I'll probably take a closer look at some point in time. And for the contents of lo.pro, I still get "." as the first subdirectory. I have to manually change it to "../core". As mentioned in my previous email, I can take a quick look whether I can see anything obvious if you upload your generated files somewhere or send them by email and tell me the paths used in your case (and whether you use a separate build dir). Michael [1] https://doc.qt.io/qtcreator/creator-sharing-project-settings.html Regards, Hossein ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi, On Thu, Feb 11, 2021 at 11:49 AM Michael Weghorn wrote: > I just double-checked it works for me with newly generated files and a > fresh Qt Creator profile taking these steps: > > 1. make sure Qt Creator is not running > > 2. Generate the IDE integration files: > > make qtcreator-ide-integration > I went through the sequence, and nothing has changed. It's a question for me: why do we need a fresh Qt Creator profile? In very rare situations, I had to clean up this profile. Also, I usually do not re-run ./autogen.sh because I didn't have any changes in the libs/configurations, and I only pulled the latest master from the git repository. This time, I re-ran autogen.sh again, and again nothing has changed. But, now I know what you're doing. I thought that only lo.pro is generated, but now I see that lo.pro.user is also being generated. That didn't help me, because the used Qt kit was not ok. I saw a manual Qt kit which is used for the configuration. It was called 'Replacement for "Desktop"', so I removed it and reconfigured the project using the appropriate kit. In this case, I had to add the previously discussed configurations manually. To create a viable solution that lasts even when you re-configure the project, I think it is needed to put all the configuration in .pro files, and not in .pro.user files, because they can be removed/changed at any time. And for the contents of lo.pro, I still get "." as the first subdirectory. I have to manually change it to "../core". I think these manual tweaks are necessary, at least for now. Regards, Hossein ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi,
On 10/02/2021 19.14, Hossein Noorikhah wrote:
I am also using "Qt Creator 4.14.0", and I am using the up-to-date git master. I
removed all the .pro.user and .pro files generated by the invocation of
"bin/gbuild-to-ide --ide qtcreator", using this tiny script:
for f in `find -name "*.pro.user"`
do
pro=${f/\.user/}
echo $f
rm $pro
rm $f
done
then regenerated .pro files using:
make qtcreator-ide-integration
and then loaded lo.pro in Qt Creator.
Sounds reasonable. I think both, *.pro.user and and *.pro files are
overwritten when running 'make qtcreator-ide-integration' anyway, so it
shouldn't even be needed to delete them explicitly.
I just double-checked it works for me with newly generated files and a
fresh Qt Creator profile taking these steps:
1. make sure Qt Creator is not running
2. Generate the IDE integration files:
make qtcreator-ide-integration
3. For reference, create archive with the autogenerated files:
tar cavf qtc_autogenerated.tar.gz $(find . -regex
'\(.*\.pro\)\|\(.*\.pro.user\)')
4. start Qt Creator with a fresh, temporary profile:
qtcreator -settingspath $(mktemp -d)
5. load project using lo.pro
6. check build and run settings
7. close Qt Creator
8. For reference, create archive with the files as they look once opened
and written back by Qt Creator:
tar cavf qtc_after_running_once.tar.gz $(find . -regex
'\(.*\.pro\)\|\(.*\.pro.user\)')
I've uploaded the archives from steps 3 and 8 here for reference:
https://nextcloud.documentfoundation.org/s/cXTdxJPw83cfTd3
The screencast at
https://nextcloud.documentfoundation.org/s/AybdcfMsSYNTSnn shows what
build and run settings look like for me in steps 5-6 and that
running/debugging LO right away basically "just works".
(In addition to the above, I'd enable system GDB pretty printers and
disable that the project is built before running every time, but that's
unrelated here.)
Can you double-check with these steps? If you send me your generated
files from steps 3 and 8, I can take a quick look whether I can see
anything obvious when comparing to my own ones.
In this stage, I had to:
1. Disable shadow build, otherwise I was getting several errors when I wanted to
build the project.
2. Remove qmake build step, otherwise I was also getting several errors when I
wanted to build the project.
I remember to have seen that previously, i.e. without the 3 patches
mentioned in my previous email. Do you have a "01-Global-Build" build
configuration for the project (as shown in the screencast) at all?
3. Change "SUBDIRS = . \" to "SUBDIRS = ../core \", otherwise I wasn't able to
see core.pro get loaded and I was getting this error message:
/path/to/libreoffice/core/lo.pro: Could not find .pro file for subdirectory
"." in "/path/to/libreoffice/core/.".
Is that in lo.pro? Mine looks different and just lists all the subdirs
by name:
SUBDIRS = UnoControls \
accessibility \
animations \
avmedia \
basctl \
basegfx \
[...]
Are you running ./autogen.sh and the build from right within the git
checkout or from a separate directory (I'm doing the former and haven't
checked the latter)?
4. Manually add the executable "instdir/program/soffice.bin", otherwise I was
getting this error message:
You need to set an executable in the custom run configuration.
Same as written for 1. and 2. above: I had the same behaviour without
the 3 patches from Sunday, but now that's prefilled as shown in the
screencast.
After doing all these steps, things were fine. So, I think all these steps are
currently necessary, unless the "bin/gbuild-to-ide" script is further tuned.
Would of course be nice if that "just worked", and I can try to take a
look once it's clear why that doesn't work for your case yet.
Michael
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi,
Thanks for your attention.
I am also using "Qt Creator 4.14.0", and I am using the up-to-date git master. I
removed all the .pro.user and .pro files generated by the invocation of
"bin/gbuild-to-ide --ide qtcreator", using this tiny script:
for f in `find -name "*.pro.user"`
do
pro=${f/\.user/}
echo $f
rm $pro
rm $f
done
then regenerated .pro files using:
make qtcreator-ide-integration
and then loaded lo.pro in Qt Creator. In this stage, I had to:
1. Disable shadow build, otherwise I was getting several errors when I wanted to
build the project.
2. Remove qmake build step, otherwise I was also getting several errors when I
wanted to build the project.
3. Change "SUBDIRS = . \" to "SUBDIRS = ../core \", otherwise I wasn't able to
see core.pro get loaded and I was getting this error message:
/path/to/libreoffice/core/lo.pro: Could not find .pro file for subdirectory
"." in "/path/to/libreoffice/core/.".
4. Manually add the executable "instdir/program/soffice.bin", otherwise I was
getting this error message:
You need to set an executable in the custom run configuration.
After doing all these steps, things were fine. So, I think all these steps are
currently necessary, unless the "bin/gbuild-to-ide" script is further tuned.
I had issues with other IDE integration outputs which need separate discussions.
Regards,
Hossein
On Wed, Feb 10, 2021 at 7:51 PM Ilmari Lauhakangas
wrote:
>
> On 10.2.2021 18.13, Michael Weghorn wrote:
> > Hi Hossein,
> >
> > thanks! Could you possibly recheck whether all of the custom steps for
> > Qt Creator setup are still necessary with an up-to-date git master?
> >
> > Those 3 commits from Sunday were meant to simplify the setup a bit
> > (automatically set up run + build configurations), so it'd be
> > interesting to hear whether that actually works for you as well (I just
> > tested with Qt Creator 4.14 myself):
> >
> > *
> > https://git.libreoffice.org/core/+/77d5383c6e83fdcb268138f71601fa39c95a62aa%5E!
> > ("qtcreator: Don't create useless run configurations for subdirs")
>
> Gitiles has some weird glitch and shows the wrong commit for two of
> these. Working link:
>
> https://git.libreoffice.org/core/commit/77d5383c6e83fdcb268138f71601fa39c95a62aa
>
> > *
> > https://git.libreoffice.org/core/+/fdd9b20572435842bde076e3c35ef94d26f13b30%5E!
> > ("qtcreator: Drop some extra whitespace in .pro.user template")
> >
> > *
> > https://git.libreoffice.org/core/+/d2d6e5c235f35bf3f2137e8dab4b9b32b72430a8%5E!
> > ("qtcreator: Show actual names for build configurations")
>
> Working link:
> https://git.libreoffice.org/core/commit/d2d6e5c235f35bf3f2137e8dab4b9b32b72430a8
>
> Ilmari
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
On 10.2.2021 18.13, Michael Weghorn wrote:
Hi Hossein,
thanks! Could you possibly recheck whether all of the custom steps for
Qt Creator setup are still necessary with an up-to-date git master?
Those 3 commits from Sunday were meant to simplify the setup a bit
(automatically set up run + build configurations), so it'd be
interesting to hear whether that actually works for you as well (I just
tested with Qt Creator 4.14 myself):
*
https://git.libreoffice.org/core/+/77d5383c6e83fdcb268138f71601fa39c95a62aa%5E!
("qtcreator: Don't create useless run configurations for subdirs")
Gitiles has some weird glitch and shows the wrong commit for two of
these. Working link:
https://git.libreoffice.org/core/commit/77d5383c6e83fdcb268138f71601fa39c95a62aa
*
https://git.libreoffice.org/core/+/fdd9b20572435842bde076e3c35ef94d26f13b30%5E!
("qtcreator: Drop some extra whitespace in .pro.user template")
*
https://git.libreoffice.org/core/+/d2d6e5c235f35bf3f2137e8dab4b9b32b72430a8%5E!
("qtcreator: Show actual names for build configurations")
Working link:
https://git.libreoffice.org/core/commit/d2d6e5c235f35bf3f2137e8dab4b9b32b72430a8
Ilmari
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Hi Hossein,
thanks! Could you possibly recheck whether all of the custom steps for
Qt Creator setup are still necessary with an up-to-date git master?
Those 3 commits from Sunday were meant to simplify the setup a bit
(automatically set up run + build configurations), so it'd be
interesting to hear whether that actually works for you as well (I just
tested with Qt Creator 4.14 myself):
*
https://git.libreoffice.org/core/+/77d5383c6e83fdcb268138f71601fa39c95a62aa%5E!
("qtcreator: Don't create useless run configurations for subdirs")
*
https://git.libreoffice.org/core/+/fdd9b20572435842bde076e3c35ef94d26f13b30%5E!
("qtcreator: Drop some extra whitespace in .pro.user template")
*
https://git.libreoffice.org/core/+/d2d6e5c235f35bf3f2137e8dab4b9b32b72430a8%5E!
("qtcreator: Show actual names for build configurations")
Regards,
Michael
On 10/02/2021 15.25, Hossein Noorikhah wrote:
Hi,
I have added some information about how to use Qt Creator for
building, running and debugging LibreOffice in the appropriate section
of the wiki:
https://wiki.documentfoundation.org/Development/IDE#Qt_Creator
I think other sections related to other IDEs also need to be revised
and improved, because not everything works out of the box in the IDEs.
Regards,
Hossein
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Added some information about Qt Creator IDE integration to the wiki
Very nice, appreciated by my anyway! On Wednesday, February 10, 2021 09:25 EST, Hossein Noorikhah wrote: Hi, I have added some information about how to use Qt Creator for building, running and debugging LibreOffice in the appropriate section of the wiki: https://wiki.documentfoundation.org/Development/IDE#Qt_Creator I think other sections related to other IDEs also need to be revised and improved, because not everything works out of the box in the IDEs. Regards, Hossein ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Added some information about Qt Creator IDE integration to the wiki
Hi, I have added some information about how to use Qt Creator for building, running and debugging LibreOffice in the appropriate section of the wiki: https://wiki.documentfoundation.org/Development/IDE#Qt_Creator I think other sections related to other IDEs also need to be revised and improved, because not everything works out of the box in the IDEs. Regards, Hossein ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
