[Libreoffice-commits] core.git: solenv/gbuildtojson solenv/gcc-wrappers soltools/mkdepend stoc/source stoc/test svl/source svtools/source toolkit/source

solenv/gbuildtojson/gbuildtojson.cxx| 34 - solenv/gcc-wrappers/g++.cxx | 14 +--- solenv/gcc-wrappers/gcc.cxx | 14 +--- solenv/gcc-wrappers/wrapper.cxx | 56

[Libreoffice-commits] core.git: solenv/gbuildtojson sot/source starmath/source stoc/source svl/source svtools/source

solenv/gbuildtojson/gbuildtojson.cxx|4 ++-- sot/source/sdstor/ucbstorage.cxx|2 +- starmath/source/ElementsDockingWindow.cxx |2 +- starmath/source/cursor.cxx |4 ++-- starmath/source/document.cxx|2 +- stoc/source

[Libreoffice-commits] core.git: 4 commits - sd/source solenv/gbuildtojson toolkit/source vcl/source

sd/source/ui/view/sdwindow.cxx |2 +- solenv/gbuildtojson/gbuildtojson.cxx |2 +- toolkit/source/awt/vclxtoolkit.cxx |1 + vcl/source/window/printdlg.cxx |2 +- 4 files changed, 4 insertions(+), 3 deletions(-) New commits: commit

Re: [Libreoffice-commits] core.git: Is gbuildtojson missing support for ExternalPackage?

Can somebody knowledgeable about gbuildtojson please look into this? Thanks, Stephan On 03/05/2017 03:10 PM, Stephan Bergmann wrote: commit d8a47a23114ce9b4a743d0da35dfb93dadc07d11 Author: Stephan Bergmann <sberg...@redhat.com> Date: Sun Mar 5 15:05:56 2017 +0100 Is gbuildtojson m

[Libreoffice-commits] core.git: bin/gbuild-to-ide solenv/gbuild solenv/gbuildtojson

bin/gbuild-to-ide | 20 - solenv/gbuild/extensions/post_GbuildToJson.mk | 18 solenv/gbuildtojson/gbuildtojson.cxx | 29 -- 3 files changed, 32 insertions(+), 35 deletions(-) New commits: commit

Re: make gbuildtojson

Hi, On Wed, Dec 28, 2016 at 09:25:48AM +0100, Jan Iversen wrote: > I see that, but I am confused, e.g. in Library_AppleRemote.mk contains: > $(eval $(call gb_Library_add_objcobjects,AppleRemote,\ > which is a .mm file Eh? There is C and C++. And there is objective C and C++. All those _four_

Re: make gbuildtojson

ension. I see that, but I am confused, e.g. in Library_AppleRemote.mk contains: $(eval $(call gb_Library_add_objcobjects,AppleRemote,\ which is a .mm file I will go through the *.mk and find all the non C++ files, and see if gbuildtojson builds correct json objects. But at least now I know why the g

Re: make gbuildtojson

Hey Jan, On Mon, Dec 26, 2016 at 12:02 PM, jan iversen <j...@documentfoundation.org> wrote: > Hi > > 2 questions about gbuildtojson. > > Currently the filenames are stripped for their type in the json file. > -ide-integration, need the filetype for each file. Can I pleas

[Libreoffice-commits] core.git: solenv/gbuildtojson

solenv/gbuildtojson/gbuildtojson.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit ae02f60cc0fb8a44addcc95d50142a57d3b8a48e Author: jan Iversen <j...@documentfoundation.org> Date: Tue Dec 27 10:47:37 2016 +0100 make the gbuildtojson output deb

make gbuildtojson

Hi 2 questions about gbuildtojson. Currently the filenames are stripped for their type in the json file. -ide-integration, need the filetype for each file. Can I please have a hint in which gb_ function the stripping happens? Considering that gbuild-to-ide.py should not be converted to C

Re: gbuildtojson and -ide-integration the continued journey.

Hey, On Sat, Dec 17, 2016 at 5:26 PM, Jan Iversen <j...@documentfoundation.org> wrote: > > Jans-iMac:work jani$ make xcode-ide-integration > make -j 8 -rs -f /Volumes/LIBREOFFICE/play/core/Makefile.gbuild > gbuildtojson > make -j 8 -rs -f /Volumes/LIBREOFFICE/play

gbuildtojson and -ide-integration the continued journey.

Hi The latest patch helped a lot, now at least the project files are generated albeit with a number of warnings. The warnings are independent of the -ide-integration selected: Jans-iMac:work jani$ make gbuildtojson make -j 8 -rs -f /Volumes/LIBREOFFICE/play/core/Makefile.gbuild gbuildtojson ld

Re: make gbuildtojson and make xx-ide-integration problems.

On Wed, Dec 14, 2016 at 04:29:16PM +0100, Michael Stahl wrote: > the problem with that is that > > > define gb_Module_add_check_target > > $(if $(filter CppunitTest_%,$(2)),$(call > > gb_Module__add_check_target_impl,$(1),$(2),$$(gb_Module_CURRENTTARGET))) > > endef > > ... expects only

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Thu, Dec 15, 2016 at 03:41:15PM +0100, Jan Iversen wrote: > Not a bad idea at all, but who pays the price for running such an > environment, that would be a rather interesting challenge for a non-profit > org. This is not the place to discuss that, which is a different topic. However,

Re: make gbuildtojson and make xx-ide-integration problems.

> Note this is _NOT_ limited to Linux only, see e.g.: > > http://www.macincloud.com/ > http://www.cloudshare.com/solutions/cloud-based-development-and-test-environments > > Not a bad idea at all, but who pays

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Thu, Dec 15, 2016 at 03:27:33PM +0100, Bjoern Michaelsen wrote: > Yes, and since, as you so eloquently pointed out, setup is still the most > tricky part of this -- at least on Windows -- I wonder if the solution is > possibly rather to double down on having properly preconfigured VMs with

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Thu, Dec 15, 2016 at 02:58:29PM +0100, Markus Mohrhard wrote: > At least from what I can see currently the two big problems that we have are > some unreliable tests, e.g. the OpenCL ones, and the brittle setup on > windows. So I think focusing on these two issues for now would help new >

Re: make gbuildtojson and make xx-ide-integration problems.

sen wrote: > > since you have already made the ball rolling by making gbuildtojson in > C++ > > the logical consequence would be to port the script to C++. > > My fear with that was it (using C++ instead of Python) would > discourage people > to contribu

Re: make gbuildtojson and make xx-ide-integration problems.

n Iversen wrote: > > since you have already made the ball rolling by making gbuildtojson in > C++ > > the logical consequence would be to port the script to C++. > > My fear with that was it (using C++ instead of Python) would discourage > people > to contribute for

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Thu, Dec 15, 2016 at 01:02:05PM +0100, Jan Iversen wrote: > since you have already made the ball rolling by making gbuildtojson in C++ > the logical consequence would be to port the script to C++. My fear with that was it (using C++ instead of Python) would discourage people to cont

Re: make gbuildtojson and make xx-ide-integration problems.

latform tool > available for this task -- even with the Python2/3 mess). > - sprinkle some fairy dust on OSX to make them ship an Python that was > releases > 8 years ago … since you have already made the ball rolling by making gbuildtojson in C++ the logical consequence would be

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Thu, Dec 15, 2016 at 12:05:38PM +0100, Michael Stahl wrote: > but we build python3 anyway, why don't we just use that to run the > bin/gbuild-to-ide script, then it'll run even on macOS? right, doing python2 (only) scripts these days is foolish as it is phasing out. FWIW, this has nothing

Re: make gbuildtojson and make xx-ide-integration problems.

> On 15 Dec 2016, at 12:32, Alexander Thurgood wrote: > > Le 15/12/2016 à 12:11, Alexander Thurgood a écrit : > > And surely the whole aim of the foo-ide-integration thing is to allow > the default to be built from within the target IDE and not to require > setting

Re: make gbuildtojson and make xx-ide-integration problems.

Le 15/12/2016 à 12:11, Alexander Thurgood a écrit : And surely the whole aim of the foo-ide-integration thing is to allow the default to be built from within the target IDE and not to require setting ENVs for frameworks that are not the default ? Alex

Re: make gbuildtojson and make xx-ide-integration problems.

Since foo-ide-integration and gbuildtojson runs with a build (directly after a make clean), that will not work. Maybe there are other ways to get python3 working with our build, but I had a mess of 2.7 header files (from apple) and 3.0 header files from an official python3 installation, and the

Re: make gbuildtojson and make xx-ide-integration problems.

ython framework on OSX 10.12.1 is python2.7 and this is what appears in the shell. The gbuildtojson script looks in workdir/GeneratedPackage directory for python3 but this isn't built by default in an OSX build because a top-level make finds python2.7 : checking for a Python interpreter with version

Re: make gbuildtojson and make xx-ide-integration problems.

On 12/15/2016 12:02 PM, Jan Iversen wrote: > >> env: python3: No such file or directory > As is says no python3, that is needed for make foo-ide-integration > > but even if you install python3, you will (at least on sierra) still have a > problem, because of a json file being generated with

Re: make gbuildtojson and make xx-ide-integration problems.

> env: python3: No such file or directory As is says no python3, that is needed for make foo-ide-integration but even if you install python3, you will (at least on sierra) still have a problem, because of a json file being generated with wrong information. rgds jan I

Re: make gbuildtojson and make xx-ide-integration problems.

Le 15/12/2016 à 11:50, Jan Iversen a écrit : > The error message is : env: python3: No such file or directory Alex ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: make gbuildtojson and make xx-ide-integration problems.

> FWIW, the xcode-ide-integration still fails for me for what appears to > be a lack of a python3 environment - OSX 10.12 default is python2.7, > which is what make finds, so I'm assuming that something in the > gbuildtojson script requires python3 ? two different things. try

Re: make gbuildtojson and make xx-ide-integration problems.

Le 15/12/2016 à 08:56, Matúš Kukan a écrit : FWIW, the xcode-ide-integration still fails for me for what appears to be a lack of a python3 environment - OSX 10.12 default is python2.7, which is what make finds, so I'm assuming that something in the gbuildtojson script requires python3 ? Alex

Re: make gbuildtojson and make xx-ide-integration problems.

On 14 December 2016 at 13:32, Jan Iversen <j...@documentfoundation.org> wrote: > I ran it in my debugger and the file in question is > '/workdir/GbuildToJson/Library/libscqahelper.dylib’ which has ‘“MAKEFILE": > "'/Volumes/LIBREOFFICE/play/core/sc/CppunitTest_sc_ucal

Re: make gbuildtojson and make xx-ide-integration problems.

om > /bin/gbuild-to-ide does not find what it expects, namely: Library_(.*)\.mk in > the MAKEFILE variable. Looking at the attached file > workdir/GbuildToJson/Library/libscqahelper.dylib it has: > > "MAKEFILE": "/Volumes/LIBREOFFICE/play/core/sc/CppunitTest_sc_ucalc.

Re: make gbuildtojson and make xx-ide-integration problems.

Hi, On Wed, Dec 14, 2016 at 01:29:28PM +0100, Jan Iversen wrote: > I have 2 problems. First problem when running “make gbuildtojson”. It seems > the linker is called in post_GbuildToJson.mk. In order to verify it I ran > “make -d gbuildtojson” (attached), where it can be seen the warn

Re: make gbuildtojson and make xx-ide-integration problems.

m-ide-integration > make -j 8 -rs -f /Volumes/LIBREOFFICE/play/core/Makefile.gbuild > gbuildtojson > cd /Volumes/LIBREOFFICE/play/core && > /Volumes/LIBREOFFICE/play/core/bin/gbuild-to-ide > --ide vim --make make > 'NoneType' object has no attribute 'group' > Tracebac

make gbuildtojson and make xx-ide-integration problems.

(RESENDING WITHOUT ATTACHMENTS) Hi Bjoern. I continued to test gbuildtojson and xx-ide-integration, but have encountered a couple of problems, where I am stuck and need help (or at least a hint where to search). My setup is Sierra (osX) and I have no problems with a full build. I have tried

Re: gbuildtojson

Hi Khaled, On Wed, 2016-12-07 at 00:46 +0200, Khaled Hosny wrote: > I used it today to build and even run the binary, but I had to edit > the > project in QtCreator and remove the qmake build step (otherwise qmake > will overwrite the Makefile and break the build). > > To run soffice I had also

Re: gbuildtojson

On Tue, Dec 06, 2016 at 11:58:08PM +0200, Maxim Monastirsky wrote: > Hi Bjoern, > > On Tue, 2016-12-06 at 15:22 +0100, Bjoern Michaelsen wrote: > > and this commit: > > > >  https://cgit.freedesktop.org/libreoffice/core/commit/?id=237a1b79a1d > > 5af10434c2b93cfc83c1c8e55a9d5 > > > > says: > >

Re: gbuildtojson

Hi Bjoern, On Tue, 2016-12-06 at 15:22 +0100, Bjoern Michaelsen wrote: > and this commit: > >  https://cgit.freedesktop.org/libreoffice/core/commit/?id=237a1b79a1d > 5af10434c2b93cfc83c1c8e55a9d5 > > says: > >  "Developers can use use QtCreator to edit, compile and debug > LibreOffice." > > I

Re: gbuildtojson

Hi, On Tue, Dec 06, 2016 at 01:41:33PM +0100, Alexander Thurgood wrote: > Yes, it would be very nice ;-) In bringing into existence such a > capability, I might actually be able to contribute more usefully to > debugging, via my QA activities, particularly awkward bugs on OSX for > which no one

Re: gbuildtojson

Le 06/12/2016 à 11:49, Bjoern Michaelsen a écrit : > > Well, I still dont quite get what your goal is. If its to bring > xcode-ide-integration on par with kdevelop-ide-inegration and > vs-ide-integration -- thats of course nice. > Yes, it would be very nice ;-) In bringing into existence

Re: gbuildtojson

Hi, On Tue, Dec 06, 2016 at 10:51:58AM +0100, Jan Iversen wrote: > However I acknowledge the fact that I am quite alone with that opinion, which > most likely means I am wrong in pursuing the goal I described. Well, I still dont quite get what your goal is. If its to bring xcode-ide-integration

Re: gbuildtojson

I never meant that the current work on gbuildtojson or x-ide-integration are bad or wrong….in my mind, it is very good, very needed work and especially the step away from interpreting the makefile output is very good, just a bit incomplete. However I acknowledge the fact that I am quite alone

Re: gbuildtojson

Hi, On Tue, Dec 06, 2016 at 08:44:04AM +0100, Jan Iversen wrote: > I might be doing something wrong, but I have until and including today, not > being able to 1/ set a breakpoint 2/ press debug 3/ stop at the breakpoint, > neither in windows nor in Xcode. This certainly is possible in Kdevelop:

Re: gbuildtojson

ction to do so is emitted when a unit test is failed. So, IMO, there is simply small polishment required to fix some shortcomings of specific integrations, in your case, Xcode. Overall, the new gbuildtojson made things much better. I don't believe ve need some "IDE build system

Re: gbuildtojson

See above, right now the Xcode-ide-integration has another problem: Jans-iMac:work jani$ make xcode-ide-integration make -j 8 -rs -f /Volumes/LIBREOFFICE/play/core/Makefile.gbuild gbuildtojson cd /Volumes/LIBREOFFICE/play/core && /Volumes/LIBREOFFICE/play/core/bin/gbuild-to-ide --ide xcode

Re: gbuildtojson

replaces it as swiftly as possible (which will be, given the size of the project, still be very slow, even though gbuildtojson and the cleanup that happened when we introduced gbuild will make it a lot easier than it was to get away from dmake). But before a/ there is a clear need to kill

Re: gbuildtojson

> Hmmm? That is already possible in most of the gbuild-to-ide created solutions > as of now e.g. KdevelopIdeIntegration has 'Full Build -- Release' (which just > calls a global make), QtCreator has '9-Global build'. Indeed, for MSVS we > currently only generate targets per module, but a 'global

Re: gbuildtojson

Hi, On Mon, Dec 05, 2016 at 08:14:30PM +0100, jan iversen wrote: > my goal is still to be able to load a solution in a IDE press build and its > done Hmmm? That is already possible in most of the gbuild-to-ide created solutions as of now e.g. KdevelopIdeIntegration has 'Full Build --

Re: gbuildtojson

reply. I will try and make a patch tomorrow. I am playing with gbuildtojson, to see if I can combine my ideas with yoursI lack (for now) one important information in your json files, and that is the dependency tree (make -d). And yes objective c++ is also wanted like java and python, my goal

Re: gbuildtojson

clean > and then > make gbuildtojson > > that gives me a strange error: > make gbuildtojson > make -rs -f /Volumes/LIBREOFFICE/play/core/Makefile.gbuild gbuildtojson > ld: warning: directory not found for option > '-L/Volumes/LIBREOFFICE/play/testNoMake/workdir/LinkTarget/S

[Libreoffice-commits] core.git: solenv/gbuild solenv/gbuildtojson solenv/qa

solenv/gbuild/extensions/post_GbuildToJson.mk |3 +++ solenv/gbuildtojson/gbuildtojson.cxx |1 + solenv/qa/python/gbuildtojson.py |2 +- 3 files changed, 5 insertions(+), 1 deletion(-) New commits: commit 65541cfaa167c9ac80af770c6034badefdc34199 Author: Bjoern

[Libreoffice-commits] core.git: Repository.mk solenv/CustomTarget_gbuildtesttools.mk solenv/Executable_gbuildtojson.mk solenv/gbuild solenv/gbuildtojson solenv/Module_solenv.mk solenv/PythonTest_solen

/extensions/post_GbuildToIde.mk | 92 +-- solenv/gbuildtojson/gbuildtojson.cxx | 104 +++ solenv/qa/python/gbuildtoide.py | 100 ++--- 8 files changed, 296 insertions(+), 41 deletions(-) New commits: commit