-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows: vs: install more dependencies #2
Comments
anarazel
added a commit
that referenced
this issue
Mar 23, 2023
Looks like the reason the deprecation failed was not specifying --project...
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 6, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 7, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 7, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 7, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 7, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
nbyavuz
added a commit
to nbyavuz/pg-vm-images
that referenced
this issue
Jun 11, 2024
It looks like vcpkg is a most correct way to install Postgres packages in Windows. There are 4 steps to install packages via vcpkg: 1- Create a base Windows image which has dependencies to run vcpkg. 2- Install packages via vcpkg and save & upload the vcpkg cache. Reuse that cache on the next install. 3- Create a Windows image from the base image (step #1). While installing packages via vcpkg, use cache from step anarazel#2. 4- Delete Windows base image. Important note: After this PR is merged, extra_*_dirs needs to be removed from Windows task in Postgres.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think adding icu, lz4, zlib, zstd would be a good minimal set.
The text was updated successfully, but these errors were encountered: