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 1saw5C-00CKuT-34 for pgsql-general@arkaria.postgresql.org; Mon, 05 Aug 2024 11:40:57 +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 1saw5A-00D4pn-Ej for pgsql-general@arkaria.postgresql.org; Mon, 05 Aug 2024 11:40:56 +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 1saw5A-00D4pe-3V for pgsql-general@lists.postgresql.org; Mon, 05 Aug 2024 11:40:56 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1saw57-003I9V-8V for pgsql-general@lists.postgresql.org; Mon, 05 Aug 2024 11:40:55 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-267b7ef154aso6669580fac.0 for ; Mon, 05 Aug 2024 04:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722858051; x=1723462851; darn=lists.postgresql.org; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FjRANZUCr/sxKJiVHJ21J5qV/8Pn8AiynLJbQsfV41I=; b=ACkivUe8+yTxWRRXPA2zqlZYwHss8GqJgKYZCCzSNfwD0/Es7sXbPo4vkPuG5wL1RT +nqgn9+nXwQ39QTcB9F1BrB3DDVddpkZMFs7dwQX/bfQydl44jQQHbaDQhPuQ6LPxCBk hgmbSHsZHvdpS/+MyD7mkwk24MSBoEIIsf8QNAc9pQJvvpT3K4m/l1+59YoPqj2sq+Vs NFV5aTaaEZwNSZQki0hWlB2tDI0FziqV3nE7he7/vkzDgrogxoXsu0viVKWLMA32cDne ZZ393eLivDT5mo4UlvgVQJLCsSEonm/owhonf2+mL1AYOyOZkALxExGXEj8QW++vMFO9 lLmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722858051; x=1723462851; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FjRANZUCr/sxKJiVHJ21J5qV/8Pn8AiynLJbQsfV41I=; b=QAEkX0Qui/NWKo4VSah2HT9AlKVcExO90n6zWr92KQ0JssUVko/MoICUGKhc0ka94N XL8+gacex8phWMkrwtnuSABHnE4FbxS0TSYpJn5+0xTMhYe5sxeAzvZ2aSN9Uch7DH3V AT5SICOKcVyPO/nIWyudh7L38w16o4C4RWt7wBvcFqud+P+MpKfuakCHdzSkSciZRO4H JZAd/gD1YD8+HK6MvRE4cbRrFqt1FuV6wmpZ2CRx5UYsphPCV5Hp3mndOpBoZolLqDH+ oCmxTQ3KykHpbgqfOVP42tfhASDOtN4Uod+iBkfLkFQ4Ujcv3uZfK45bctDPAfCNML2y 5acQ== X-Gm-Message-State: AOJu0Ywi+l0qlj4kyo4xiberTehrEExZNduzKcMBH+f3kg1ucx1tPwmx B5xB0s4Y9YPwSSXj9XH53pYlXUIJIzKKurJyW89WxPFq+i1BGqx31EVw521sX6kgmK5V5KQSlTj UokBwKP7EvuR1KjexcBXIPHX9WA+k9cCB X-Google-Smtp-Source: AGHT+IE3Mv4rEY9K3RQIVU0YEp3i/eDjJOsP/p8JX5ur5jhqzS8huK0UAEIw5Xf/7p7KHc4BBNlw1RXE9tFitpxQJmA= X-Received: by 2002:a05:6870:c095:b0:25e:11f4:f694 with SMTP id 586e51a60fabf-26891d48638mr15074817fac.21.1722858051072; Mon, 05 Aug 2024 04:40:51 -0700 (PDT) MIME-Version: 1.0 From: Dominique Devienne Date: Mon, 5 Aug 2024 13:40:40 +0200 Message-ID: Subject: Building v17 Beta2 on Windows To: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi. I'm using as the go-between for a colleague that's not subscribed to this ML. In short, we have Python-based automation scripts to build our 3rd parties. And the ones we have, that worked fine with v16, do not with v17 beta2, on Windows. Thus I'm asking for advice as how we should proceed. TIA, --DD PS: My colleague also mentioned finding posts about a change around a Meson build??? Is that now required? Any documentation / release notes regarding such a change? PPS: Our intent was to test the new wait-on-socket API discussed with Tom recently. ----------------8<-------------------- From my colleague I tried to build the Linux and Windows PostgreSQL 17beta2 devkits. For that I downloaded the source code from: https://www.postgresql.org/ftp/source/v17beta2/ And tried to use the python builders we have to build PostgreSQL devkits in an automated way. No problem on Linux platform, but the build on Windows platform failed. We used to proceed this way to build the Windows devkit using VS2022 In the PostgreSQL source folder: * Cd src\tools\msvc * Create a config.pl file containing a line to locate the OpenSSL devkits * Run: .\build.bat [DEBUG] The issue is that, in the PostgreSQL source dir installed from https://www.postgresql.org/ftp/source/v17beta2/ postgresql-17beta2.tar.gz, there is no src/tools/msvc folder. I looked for a Windows 17beta2 package to download, but only saw Postgresql 16 version: https://www.postgresql.org/docs/current/install-windows-full.html There is no mention of Windows OS. neither in https://www.postgresql.org/download/snapshots/ nor in https://www.postgresql.org/download/windows/ So for the moment, I don=E2=80=99t know how to proceed