Skip to content

Makefile.am: drop vc10, vc11 and vc12 from the dist tarball#12288

Closed
bagder wants to merge 2 commits into
masterfrom
bagder/vc-eol-dist
Closed

Makefile.am: drop vc10, vc11 and vc12 from the dist tarball#12288
bagder wants to merge 2 commits into
masterfrom
bagder/vc-eol-dist

Conversation

@bagder

@bagder bagder commented Nov 7, 2023

Copy link
Copy Markdown
Member

They are end of life products. Support for generating them remain in the repo for a while but this change drops them from distribution.

They are end of life products. Support for generating them remain in the
repo for a while but this change drops them from distribution.
@bagder bagder added build Windows Windows-specific dist labels Nov 7, 2023
@bagder bagder closed this in 3d93d18 Nov 7, 2023
@bagder bagder deleted the bagder/vc-eol-dist branch November 7, 2023 10:34
@MarcelRaad

Copy link
Copy Markdown
Member

These old versions were actually the only use case I still saw for the project files at all as CMake removed support for generating them for VC 10 and 11, and deprecated VC 12. Newer Visual Studio versions even come with CMake.

@bagder

bagder commented Nov 7, 2023

Copy link
Copy Markdown
Member Author

No one would be happier than me if we would remove them all from both git and the dist, but are our users ready for that?

@jay

jay commented Nov 8, 2023

Copy link
Copy Markdown
Member

I'm still using the vc10 and vc12 projects on some older computers. I switch between builds a lot and SSL libraries using the configuration drop down. I can re-generate if necessary but a lot of the time it isn't necessary. Like for example if no file is added I usually don't have to regenerate. If I want to switch between OpenSSL and WinSSL (Schannel) I don't have to regenerate. If I want to switch between 64/32 or release/debug I don't have to regenerate. And so on. I just choose from the drop down. The project configurations are very basic and had to I write a script to enable http2. As for users that may be using the old versions I don't know if that's happening. I see no reason to disable generating them for distribution if they're going to remain in the repo. I guess we'll find out if anyone makes a report about it.

@bagder

bagder commented Nov 8, 2023

Copy link
Copy Markdown
Member Author

I can re-generate if necessary but a lot of the time it isn't necessary.

I would imagine that most curl developers need that rather than to have them shipped in the tarball as we do change the source file set every once in a while.

I see no reason to disable generating them for distribution if they're going to remain in the repo.

It's a gradual thing. Let's first see if anyone even notices this step.

vszakats added a commit to vszakats/curl that referenced this pull request Jan 12, 2026
Most files were removed 2 years ago, the remaining two do not work
without those.

Follow-up to 3d93d18 curl#12288
vszakats added a commit that referenced this pull request Jan 12, 2026
Most files were removed 2 years ago, the remaining two do not work
without those.

Follow-up to 3d93d18 #12288

Closes #20272
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build dist Windows Windows-specific

Development

Successfully merging this pull request may close these issues.

3 participants