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_ case

Re: make gbuildtojson

> > As an example any object mentioned with add_exception_objects is a c++ file > with the cxx file extension and exceptions being enabled. In contrast > add_cobjects is e.g. a c file with a .c extension and add_objcxxobjects is a > objective-c file with a .mm file extension. I see that, but

Re: make gbuildtojson

Hey Jan, On Mon, Dec 26, 2016 at 12:02 PM, jan iversen 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 please have a > hint in which gb_ function the stripping hap

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++, wo

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 CppunitT

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, it

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 t

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 > pe

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

On 12/15/2016 02:58 PM, Markus Mohrhard wrote: > On Thu, Dec 15, 2016 at 1:33 PM, Bjoern Michaelsen > > wrote: > > Hi, > > On Thu, Dec 15, 2016 at 01:02:05PM +0100, Jan Iversen wrote: > > since you have already made the ball rolling by making g

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

Hey, so with the experience of writing one of the ide integrations and helping people especially during the night some comments. On Thu, Dec 15, 2016 at 1:33 PM, Bjoern Michaelsen < bjoern.michael...@canonical.com> wrote: > Hi, > > On Thu, Dec 15, 2016 at 01:02:05PM +0100, Jan Iversen wrote: > >

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 contribute

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

> - let go of that requirement on OSX where getting python3 is a hassle > (its no issue on Linux, neither on Windows as long as we need cygwin anyway) > - use something different than Python3 for bootstrapping the env > (then again: What? Python is probably the bestsuited tool crossplatform tool

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 ENVs for frameworks that are

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.

> > 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? I can only look at my configuration, where tml_ helped me, and I needed to have --enable-python=fully-internal in autogen.input to make a full build work. Since foo-id

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

Le 15/12/2016 à 11:50, Jan Iversen a écrit : > > > If your make does not fail with a python backtrace, then you have another > problem, like missing python3. > Did I misunderstand something, as I don't recall python3 becoming a requirement for building LO ? The default python framework on OSX

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 wron

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.

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 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_ucalc.mk’”’ (see > attachment GbuildToJson.tgz). /me wonders why

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

On 12/14/2016 04:23 PM, Bjoern Michaelsen wrote: > On Wed, Dec 14, 2016 at 01:29:28PM +0100, Jan Iversen wrote: >> File "/Volumes/LIBREOFFICE/play/core/bin/gbuild-to-ide", line 136, in >> __lib_from_json >> >> GbuildParser.libpattern.match(os.path.basename(json['MAKEFILE'])).group(1), >> A

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.

Hey Jan, On Wed, Dec 14, 2016 at 1:32 PM, Jan Iversen wrote: > (RESENDING WITHOUT ATTACHMENTS) > > > > 2) xx-ide-integration > I have test with Xcode and vim, same result (clearly because error occurs > during startup. > > make vim-ide-integration > make -j 8 -rs -f /Volumes/LIBREOFFICE/play/co

make gbuildtojson and make xx-ide-integration problems.

to reduce the build as much as possible (see attached autopen.input). I check with a patched post_GbuildToJson.mk (attached) based on your recommendations. I have 2 problems. First problem when running “make gbuildtojson”. It seems the linker is called in post_GbuildToJson.mk. In order to verify