Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mXKyl-0000Qo-Q9 for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Oct 2021 10:13:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mXKyk-0003k4-9A for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Oct 2021 10:13:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mXKyj-0003jw-U0 for pgsql-hackers@lists.postgresql.org; Mon, 04 Oct 2021 10:13:50 +0000 Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mXKyh-0005lM-D9 for pgsql-hackers@postgresql.org; Mon, 04 Oct 2021 10:13:49 +0000 Received: by mail-wm1-x330.google.com with SMTP id g198-20020a1c20cf000000b0030d60cd7fd6so4299248wmg.0 for ; Mon, 04 Oct 2021 03:13:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=lDtwZK1wrtGwuh9aO3aHn1J48JpE415FU0HvxxnWzlk=; b=sdMt+ksvj1GFfnsba1uGFLdWKRMQF2nf41FnI/mt2FSqMWThNX6S8uo9TkD5Zcl8Bb iNcg0dWX6YouyK5h8GYrYT8bkb+w/Wyrv0tnAGBj1CRDiTeDQTjDSfgIPJEHAKMnNwzz ZjCbzwYHqvH6y4ju6HAIXyLGQL3uLmYeZov8WaAFuOi+Uu/hoPyV7TLe9D3UErqz2ExM pN+V0nKMtCVn+Hnbyp99AA6bedx1upWK5DwTulCNr/MeCPKwx5iPBEVXvAGJGk/e9iiN OfsWIKgi0Y3AO/NF5i/qKcJRR8bBjHDOB17xFZNoEGVprtDnKYfk6MGPTzq21ddzKjV9 iEhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=lDtwZK1wrtGwuh9aO3aHn1J48JpE415FU0HvxxnWzlk=; b=jWgGHga1ytnQWFhgS8sWkvxp21Lkp+HjBcew9oQLzXV12adOX329WHuNbiVXpSOliI DwyWT/8MIKrjai4NP/5xPoXHp9CG92D78I0ATVZ6r3vBmgWirNb26VXnF3HaRBdeStmJ Eb8ekpfh7YdvP5enuOHmRG6yC0B97sRlf3zDeNBhQFa3SFz4xsDJ34PFb/U4Ojpn8scw 2PpUPNi9SgszvipbxKtbImHKgqMOWNpjU3Da1XL569cDy8cp6X1cNFUAER/ImCDjvawf F7t2ecE9QGTIZPgiJgR7kIzcfvGH6NxA6UCpQaoF7OS1wvataQUoFwcMVbU2la5k6qly w+jw== X-Gm-Message-State: AOAM5308ewMkBMP8kYNllF0xjlnaEs3uFCj2xRDPPk1ODA9YULdoyp9Q SBB93vtsp/58ghDxFiRKvpGeBw== X-Google-Smtp-Source: ABdhPJzXjgUyfhXHiqqK9DVHfXd9Sk3QxggvRUP3bBznvo11KcShcaosZ/oGf2STl1b0+65PhG7XBg== X-Received: by 2002:a7b:c14d:: with SMTP id z13mr12063633wmi.112.1633342425911; Mon, 04 Oct 2021 03:13:45 -0700 (PDT) Received: from localhost.localdomain (dynamic-e41ppu12g47187sxo-pd01.res.v6.highway.a1.net. [2001:871:5c:e7da:d95f:605c:c07:aa3c]) by smtp.gmail.com with ESMTPSA id 73sm645059wmb.40.2021.10.04.03.13.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Oct 2021 03:13:45 -0700 (PDT) Message-ID: <42c75bedf19369a5bcd3263b227f40e461d5b8a0.camel@cybertec.at> Subject: Re: VS2022: Support Visual Studio 2022 on Windows From: Laurenz Albe To: Hans Buschmann , "pgsql-hackers@postgresql.org" Date: Mon, 04 Oct 2021 12:13:45 +0200 In-Reply-To: <1633101364685.39218@nidsa.net> References: <1633101364685.39218@nidsa.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2021-10-01 at 15:15 +0000, Hans Buschmann wrote: > During testing of the new Visual Studio 2022 Preview Version 4.1 from Microsoft I also tried PG14.0 on it. > The x64 version built without error!. > > Even when this is only a preview version (the real thing is to expected soon) it seems appropriate to include the support to Postgres msvc tools directory. > > I followed the guideline of the patch msvc-2019-support-v4.patch for VS2019 support. New patch attached. [...] > HELP NEEDED: > > Please could somebody test the patch and enter it to the next commit fest? Thanks for that work; help with Windows is always welcome. Please go ahead and add the patch to the commitfest yourself. Testing will (hopefully) be done by a reviewer who has access to MSVC 2022. Yours, Laurenz Albe