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 whol
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 differ
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-wo
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 u
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
probl
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( |$)'
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
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-integrat
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 with
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/l
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
patch
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 s
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
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 Hoss
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 unavoi
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
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
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-in
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 "*.pr
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
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 + bui
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
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/De
23 matches
Mail list logo
