From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
Subject: | Re: the ScriptingMojo |
Date: | 2020-08-27 13:30:21 |
Message-ID: | 5F47B56D.4080703@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
On 08/27/20 07:52, Kartik Ohri wrote:
> It seems there is some issue in linking but the logs do not hint this.
> Another possible reason could be the packaging module not being able to
> find the .dll. But again no sign of this from the logs. Do you have any
> idea about what could be the issue here ?
The naming of the link target has different conventions depending on
the os. On Unix-like systems, it has a 'lib' prefix and extension .so
On Mac the .so extension changes to .bundle (except that in PostgreSQL's
PGXS they keep .so instead, which we now have the option of changing to,
but we've used the Mac convention of .bundle for several years).
On Windows, the extension changes to .dll and the lib prefix goes away.
You can see these names in the different profiles that set module.pathname
in -packaging/pom.xml. It has to explicitly add .bundle on Mac (because
PostgreSQL would otherwise assume .so). On Windows, it doesn't have to add
.dll (because that is the assumed extension on Windows), but it does drop
the lib prefix.
Your build has produced a file that ends with .dll but still has the lib
prefix.
Regards,
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | Kartik Ohri | 2020-08-27 16:24:38 | Re: the ScriptingMojo |
Previous Message | Kartik Ohri | 2020-08-27 13:17:23 | Re: the ScriptingMojo |