agora inbox for pljava-dev@postgresql.org
help / color / mirror / Atom feedSubject: [Pljava-dev] Source code move to Git
Date: Mon, 14 Jan 2013 06:20:02 -0800
Message-ID: <A496216A-792E-4976-85F3-4465359EECD6@me.com> (raw)
In-Reply-To: <50F3D831.5090206@tada.se>
References: <50F27A01.2090003@tada.se>
<A2FF70FC-EE5D-4F43-ACE8-A6F73366E314@me.com>
<50F2FAEA.6090809@tada.se>
<B38CBAB7-8CA3-4E1A-8BC0-408FA8429F87@me.com>
<2C6DA4B8-9C38-4AEF-97FA-BEDB1839861D@me.com>
<50F3762E.7030500@2ndQuadrant.com>
<8EBAEA33-06CB-4F2E-B7D3-D2F51474734C@me.com>
<50F3852F.60901@2ndQuadrant.com>
<50F3D831.5090206@tada.se>
Haven't looked at it, but it does look quite good. Seems like its worth a go at it.
Sent from my Tricorder
On Jan 14, 2013, at 2:04 AM, Thomas Hallgren <thomas at tada.se> wrote:
> Has any of you looked at the maven-nar-plugin? Seems it might be capable to even out some of the quirks when building on different platforms. http://duns.github.com/maven-nar-plugin/. My idea was to somehow use it in conjunction with PGXS.
>
> A functional Windows build is a must of course but I'd be totally fine if MinGW was stripped out of the equation in favor of more "proper" ways of doing it.
>
> The support for GCJ can be dropped as far as I'm concerned. I think that project stalled some three-four years ago.
>
> - thomas
>
>
> On 2013-01-14 05:10, Craig Ringer wrote:
>> On 01/14/2013 12:04 PM, Hal Hildebrand wrote:
>>> You can execute anything from Maven using the exec maven plugin (http://mojo.codehaus.org/exec-maven-plugin/). There's a specialization for executing Ant, if that's useful (https://maven.apache.org/plugins/maven-antrun-plugin/). So, the mechanics of integrating Make aren't especially difficult.
>>>
>>> The bigger difficulty, from my POV, is setting up the environment correctly. Having done this a couple of times, it still seems like quite the chore to actually build the C portion of pl/java. I'm not sure if that's just inherent difficulty or if there's something that can be done to make the process painless. I'm guessing the former because that's the way C programs roll.
>> It "just worked" for me, thanks to PGXS. Put `pg_config` on the PATH and run "make", it just builds.
>>
>> Were you trying to build the sources directly, without using the PGXS integration - say via some other build system instead of using the makefiles?
>>
>> One thing that worries me is that AFAIK PGXS doesn't work with the Visual Studio builds on Windows. The PL/Java builds for Windows seem to be compiled with MinGW, which is kind of ugly when Pg is built with MSVC. I haven't looked into what's involved in building extensions out-of-tree on Windows yet as I've always just moved them into contrib/ in the source tree and built them as part of a PostgreSQL source build.
>>
>> --
>> Craig Ringer http://www.2ndQuadrant.com/
>> PostgreSQL Development, 24x7 Support, Training & Services
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130114/f339ef4c/attachment.html;
view thread (20+ messages) latest in thread
Message-ID: <A496216A-792E-4976-85F3-4465359EECD6@me.com>
Permalink: ../A496216A-792E-4976-85F3-4465359EECD6@me.com/
Also on: postgresql.org/message-id/A496216A-792E-4976-85F3-4465359EECD6@me.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pljava-dev@postgresql.org
Subject: Re: [Pljava-dev] Source code move to Git
In-Reply-To: <A496216A-792E-4976-85F3-4465359EECD6@me.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox