Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJaER-005ib4-EL for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 14:54:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJaEO-00Eisb-18 for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 14:54:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJaEN-00EisD-A5 for pgsql-hackers@lists.postgresql.org; Tue, 18 Jun 2024 14:54:44 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJaEJ-002IjM-Qj for pgsql-hackers@lists.postgresql.org; Tue, 18 Jun 2024 14:54:43 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2ebe3bac675so49733811fa.1 for ; Tue, 18 Jun 2024 07:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1718722479; x=1719327279; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FGSLH3OL0xcacaiHDWwnAn6kJcDTEsA9sQMUweOyHaE=; b=KZHL3dKs9JE0J3bBriUZ6TvBJPqebLTWpM/2bXHvNQCa2oxpftdMVq88Vcb3HxWrxO GfACF01Lsi76TZLLILzTGJJA023blwgR5oN0jsZRLNcwE68fnM5g3n3urfHg5qeK5df4 +TikG9dlWfNYzE0JUCmI6zPRZ8qj7/Z4EZV3U1OKhgh1cE0ab53DU7Kb1Y2nACEJ/KU+ UvRq6O4QjYubYvwFmrNTyCWGEZ3W0s0G6uGRV3SCl0KUM6f6YKMriwC7BQdUvOvp72kj /IxCNbdAof8XA9LwTB6PvwWgdXGDY7BM7gXTIiglCRK2UN8aGTMME8GFueK2nguwHdS9 NOzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718722479; x=1719327279; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FGSLH3OL0xcacaiHDWwnAn6kJcDTEsA9sQMUweOyHaE=; b=bmqw3XthCXfew6L9xLXx2Rzuzy/qMu8spmc5ON9NZQt6xGFIX0kFZ5uAEGbEIOmp1M r4lPpN526tsMhUaVgLJB3iCe4ffe1e+ruIE8Nk9mJG8fce5MP6UjslAgUJolt4V8leFF BB6JNxJ1MhT4SHzK/8Vt2826m3Kt5KaytTYKdhn97oUpeee7kOcwVnDyN9UfMY1/gHez PJG+wuETpnQkNZ1sv7zvK49dJwQVhOzeK1BYmBOsEfV5O+DjnVVTtYjUUjzRIMhIqIQN oa6Q6rGc4oMYTOMmoSHQE6Zo9ujjrowsGPx92VpvHE/pMggNFQLa+BZtZ0DPH7QT1ARh DOsQ== X-Gm-Message-State: AOJu0Yw93u75VKQmNYlQ3hYTXHDC5Yh2P2jMvxWrRicGY+x/OpfEAB9M rKUtDNIKvF6DDPkEkNeV3atZVT9frF+zEh5f9282jKW28WSyh3TZyOCxtdYXKuuTKMVuCbHt9Mh yEDMda5BGJYDFU1DF3PtcL+RfYuKKH9jWoKeN+SgCZkLVy+DjoQ== X-Google-Smtp-Source: AGHT+IEmQRTSpUKUipnUVsgEfMsVFWUEcA0ZTIz/O4X62T3VSIZECZXXy9B+29realqpPtubFj3o+NFwJrFWX5ddgSs= X-Received: by 2002:a2e:b306:0:b0:2ea:e39f:aae9 with SMTP id 38308e7fff4ca-2ec346658c6mr7958191fa.11.1718722478620; Tue, 18 Jun 2024 07:54:38 -0700 (PDT) MIME-Version: 1.0 References: <20240618143850.nl67cwctsodmgfpi@awork3.anarazel.de> In-Reply-To: <20240618143850.nl67cwctsodmgfpi@awork3.anarazel.de> From: Dave Page Date: Tue, 18 Jun 2024 15:54:27 +0100 Message-ID: Subject: Re: Meson far from ready on Windows To: Andres Freund Cc: PostgreSQL Developers Content-Type: multipart/alternative; boundary="000000000000ce57cb061b2b4239" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ce57cb061b2b4239 Content-Type: text/plain; charset="UTF-8" Hi On Tue, 18 Jun 2024 at 15:38, Andres Freund wrote: > Hi, > > On 2024-06-18 14:53:53 +0100, Dave Page wrote: > > My next task was to extend that to support PostgreSQL 17 and beyond, > which > > is where I started to run into problems. I've attempted builds using > Meson > > with each of the dependencies defined in the old-style config.pl, both > with > > and without modifying the INCLUDE/LIBS envvars to include the directories > > for the dependencies (as was found to work in the previous discussion re > > zlib): > > > > Will not successfully configure at all: > > Do you have logs for those failures? > Sure - https://developer.pgadmin.org/~dpage/build-logs.zip. Those are all without any modifications to %LIB% or %INCLUDE%. > I think it's important to note that Meson largely seems to want to use > > pkgconfig and cmake to find dependencies. pkgconfig isn't really a thing > on > > Windows (it is available, but isn't commonly used), and even cmake would > > typically rely on finding things in either known installation directories > > or through lib/include vars. > > I am not really following what you mean with the cmake bit here? > > You can configure additional places to search for cmake files with > meson setup --cmake-prefix-path=... > None of the dependencies include cmake files for distribution on Windows, so there are no additional files to tell meson to search for. The same applies to pkgconfig files, which is why the EDB team had to manually craft them. > > > > There really aren't standard directories like > > /usr/lib or /usr/include as we find on unixes, or pkgconfig files for > > everything. > > Yes, and? > And that's why we really need to be able to locate headers and libraries easily by passing paths to meson, as we can't rely on pkgconfig, cmake, or things being in some standard directory on Windows. Thanks. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com --000000000000ce57cb061b2b4239 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Tue, 18 Jun 2024 at 15:38, Andres Freund <andres@anarazel.de> wrote:
Hi,

On 2024-06-18 14:53:53 +0100, Dave Page wrote:
> My next task was to extend that to support PostgreSQL 17 and beyond, w= hich
> is where I started to run into problems. I've attempted builds usi= ng Meson
> with each of the dependencies defined in the old-style config.pl, both with=
> and without modifying the INCLUDE/LIBS envvars to include the director= ies
> for the dependencies (as was found to work in the previous discussion = re
> zlib):
>
> Will not successfully configure at all:

Do you have logs for those failures?

Su= re -=C2=A0h= ttps://developer.pgadmin.org/~dpage/build-logs.zip. Those are all witho= ut any modifications to %LIB% or %INCLUDE%.


> I think it's important to note that Meson largely seems to want to= use
> pkgconfig and cmake to find dependencies. pkgconfig isn't really a= thing on
> Windows (it is available, but isn't commonly used), and even cmake= would
> typically rely on finding things in either known installation director= ies
> or through lib/include vars.

I am not really following what you mean with the cmake bit here?

You can configure additional places to search for cmake files with
meson setup --cmake-prefix-path=3D...

N= one of the dependencies include cmake files for distribution on Windows, so= there are no additional files to tell meson to search for. The same applie= s to pkgconfig files, which is why the EDB team had to manually craft them.=
=C2=A0


> There really aren't standard directories like
> /usr/lib or /usr/include as we find on unixes, or pkgconfig files for<= br> > everything.

Yes, and?

And that's why we really = need to be able to locate headers and libraries easily by passing paths to = meson, as we can't rely on pkgconfig, cmake, or things being in some st= andard directory on=C2=A0Windows.

Thanks.

--
--000000000000ce57cb061b2b4239--