The new changes include simply adding a printf statement and it's not
working.
On Fri, 21 Aug, 2020, 1:10 AM anshu khare, wrote:
> Hi
>
>
>
> I checked git status and I could clearly see modified files.
>
> So I restored them all.
>
> Then I again went to the build folder in C drive. I saw tha
Hi
I checked git status and I could clearly see modified files.
So I restored them all.
Then I again went to the build folder in C drive. I saw that the changes to
the code which I did in the the first build were gone.
Then I again built the debug version on libreoffice.sln in visual Studio.
On Thu, 20 Aug 2020 at 22:41, anshu khare wrote:
>
> I basically ran autogen.sh , /opt/lo/bin/make gb_color=1,
> instdir/program/soffice.exe, and /opt/lo/bin/make vs2019-ide-integration
> again on Cygwin.
>
You don't need to run autogen.sh every time. That is only for the first
build. The normal
When I built libreoffice earlier I did some changes in the code.
I built libreoffice again using this link.
https://wiki.documentfoundation.org/Development/BuildingOnWindows
I didn't build from scratch.
I basically ran autogen.sh , /opt/lo/bin/make gb_color=1,
instdir/program/soffice.exe, and
When I built libreoffice earlier I did some changes in the code.
I built libreoffice again using this link.
https://wiki.documentfoundation.org/Development/BuildingOnWindows
I didn't build from scratch.
I basically ran autogen.sh , /opt/lo/bin/make gb_color=1,
instdir/program/soffice.exe, and
anshu khare kirjoitti 20.8.2020 klo 18.23:
Hi
I was having my end-term exams. So I couldn't be active during that time.
Recently, I installed libreoffice again on windows. But when I built it,
I saw that the previously installed libreoffice was getting built rather
than the new one.
Could s
