MIME-Version: 1.0
References: 
 <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
 <5F3A7DC6.8090905@anastigmatix.net>
 <CAASLQ4PEgo5Nj0EVsOfGoB96dQFXfFYxrrB0rS1wdad7x_E5fA@mail.gmail.com>
 <CAASLQ4OowXOmnbbbT0Wh1ZkB4h=6JQfC61ojmN07EYnO0QCcow@mail.gmail.com>
 <5F3D32E9.80504@anastigmatix.net> <5F3D36BE.70703@anastigmatix.net>
 <5F3D38F8.7050907@anastigmatix.net> <5F3D3A75.5010304@anastigmatix.net>
 <5F3D3D2E.4070109@anastigmatix.net> <5F3D43BD.4020900@anastigmatix.net>
 <5F3DA48D.7090408@anastigmatix.net>
 <CAASLQ4MBWQeFLdAPNcsgcpLyekU5X=ExQUuGgE49AUFdEYJr8g@mail.gmail.com>
 <5F41943D.9080707@anastigmatix.net>
 <CAASLQ4P5oEx0DLoDLEOAkZSwffU2eS2+NKbevgYqpknHGucaTw@mail.gmail.com>
 <5F427604.5010103@anastigmatix.net>
 <CAASLQ4Nr3MPQuZziVU+89ULZ=BgQjaPPnCLsyPR3mhW-eWoOBw@mail.gmail.com>
 <5F42A71F.8000002@anastigmatix.net>
 <CAASLQ4PkP017rtyUswKO_TCiNmnica-nrQHBgggFw-U_9MstUg@mail.gmail.com>
 <5F459B6E.3020803@anastigmatix.net>
 <CAASLQ4P47TNiEsuj3ga-vuYeCSBJZmHrPM-49E-X=0T5RTmhKw@mail.gmail.com>
 <5F45EE7F.5020609@anastigmatix.net>
In-Reply-To: <5F45EE7F.5020609@anastigmatix.net>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Wed, 26 Aug 2020 22:25:08 +0530
Message-ID: 
 <CAASLQ4MH5JaVbrG9O_S+9dnp=tj_8N3jArxxpf-dJD1ezd5SfQ@mail.gmail.com>
Subject: Re: the ScriptingMojo
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000081265205adcab029"
Precedence: bulk

--00000000000081265205adcab029
Content-Type: text/plain; charset="UTF-8"

Hi,

> Yes ... because not only is it done by the nar-maven-plugin (which is not
> what we want to imitate), it is also done that way by the PGXS makefiles
> (which are what we want to imitate). In fact it has been the usual practice
> for about as long as there have been makefiles.
>
> One reason is that compiling C programs is a kind of local activity.
> Each .c file is transformed into a .o file, without needing to know
> very much about the others. (What little it does need to know, it
> gets from .h files.)
>
> Conceptually, it's a different operation once you have all of those .o
> files and you want to edit and link all of them together into some kind
> of binary image with the references resolved. On top of that, there are
> choices in what kind of result to produce. A standalone executable?
> A static library? A dynamic library? A loadable plugin? (The Mac OS
> linker really makes a distinction between a regular dynamic library
> and a plugin. The unresolved references in a dynamic library have to
> be findable in the other libraries given as its dependencies. For a
> plugin, the assumption is they will be findable in the program that
> the plugin gets loaded into. The Mac linker actually checks that at
> link time, which is why there is a -bundle_loader option added in
> the Mac OS profile in pljava-so.)
>
> Even when you can just pile all the compiling and linking options onto
> one gcc command line, that still is just the gcc wrapper command being
> clever and sorting the options out and running the preprocessor and
> compiler and then the linker. But for clarity in makefiles, it is very
> common to separate the rules for compiling the components from the rules
> for linking the final product.
>

Understood, that makes sense.
-------------------------------------------
I have made some progress on the plugin. The Mac OS X configuration is
working and passing the CI. I have also begun work on completing the
Windows configuration. I am having some issues with the File.separator
being used in paths. Once I am able to resolve it, we should have all the
basic functionality ready. Also, I noticed that running pg_config in the
Windows command line (MSVC) environment gives values of cc, cflags and
ldflags so on as not recorded.
Thanks.
Regards,
Kartik

--00000000000081265205adcab029
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"></div>Hi,<br><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">Yes ... because not only i=
s it done by the nar-maven-plugin (which is not<br>
what we want to imitate), it is also done that way by the PGXS makefiles<br=
>
(which are what we want to imitate). In fact it has been the usual practice=
<br>
for about as long as there have been makefiles.<br>
<br>
One reason is that compiling C programs is a kind of local activity.<br>
Each .c file is transformed into a .o file, without needing to know<br>
very much about the others. (What little it does need to know, it<br>
gets from .h files.)<br>
<br>
Conceptually, it&#39;s a different operation once you have all of those .o<=
br>
files and you want to edit and link all of them together into some kind<br>
of binary image with the references resolved. On top of that, there are<br>
choices in what kind of result to produce. A standalone executable?<br>
A static library? A dynamic library? A loadable plugin? (The Mac OS<br>
linker really makes a distinction between a regular dynamic library<br>
and a plugin. The unresolved references in a dynamic library have to<br>
be findable in the other libraries given as its dependencies. For a<br>
plugin, the assumption is they will be findable in the program that<br>
the plugin gets loaded into. The Mac linker actually checks that at<br>
link time, which is why there is a -bundle_loader option added in<br>
the Mac OS profile in pljava-so.)<br>
<br>
Even when you can just pile all the compiling and linking options onto<br>
one gcc command line, that still is just the gcc wrapper command being<br>
clever and sorting the options out and running the preprocessor and<br>
compiler and then the linker. But for clarity in makefiles, it is very<br>
common to separate the rules for compiling the components from the rules<br=
>
for linking the final product.<br></blockquote><div><br></div><div>

Understood, that makes sense.</div><div>-----------------------------------=
--------</div><div>I have made some progress on the plugin. The Mac OS X co=
nfiguration is working and passing the CI. I have also begun work on comple=
ting the Windows configuration. I am having some issues with the File.separ=
ator being used in paths. Once I am able to resolve it, we should have all =
the basic functionality ready. Also, I noticed that running pg_config in th=
e Windows command line (MSVC) environment gives values of cc, cflags and ld=
flags so on as not recorded.</div><div>Thanks.</div><div>Regards,</div><div=
>Kartik</div></div></div>

--00000000000081265205adcab029--