Skip to content
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

Drop support for MinGW #4601

Merged
merged 4 commits into from
Feb 14, 2020
Merged

Drop support for MinGW #4601

merged 4 commits into from
Feb 14, 2020

Conversation

steven-johnson
Copy link
Contributor

@steven-johnson steven-johnson commented Feb 10, 2020

Not sure if we are ready for this yet or not, but here's a PR that removes all the MinGW if we decide to go that way. (Note that a separate PR for the buildbots will be necessary as well.)

Fixes #4593

Not sure if we are ready for this yet or not, but here's a PR that removes all the MinGW if we decide to go that way. (Note that a separate PR for the buildbots will be necessary as well.)
README.md Outdated
@@ -133,8 +133,7 @@ To configure and build Halide:

#### Building Halide and LLVM on Windows using mingw

The makefile method above should work from inside a "mingw64" shell
(not the default shell) in an msys2 installation.
Halide no longer supports building via the Makefile under mingw. Windows users should use the CMake build process instead.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment can be misinterpreted to mean that mingw is supported via cmake. We should just delete the mingw section.

@steven-johnson steven-johnson marked this pull request as ready for review February 10, 2020 21:56
Makefile Outdated
else
MAP_FLAGS= -Wl,-Map=$(BUILD_DIR)/llvm_objects/list.all
LIST_OUTPUT = > /dev/null
endif
endif

$(BUILD_DIR)/llvm_objects/list: $(OBJECTS) $(INITIAL_MODULES)
# Determine the relevant object files from llvm with a dummy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be more simplified if we don't support MinGW: We can get rid of LIST_OUTPUT and in line 985 always pipe to /dev/null.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Also the removal of xargs later in the file.

@shoaibkamil
Copy link
Contributor

I'm not sure if we should do this yet, but the PR does make a good case that removing MinGW simplifies several pieces of the build process. Otherwise LGTM.

Perhaps we should send a message on the halide-dev list as you suggested?

@steven-johnson
Copy link
Contributor Author

Perhaps we should send a message on the halide-dev list as you suggested?

Done, a couple days ago. No responses as of yet.

@steven-johnson
Copy link
Contributor Author

So far, not a single complaint about this proposal. How long should we wait for feedback?

@shoaibkamil
Copy link
Contributor

I don't think we should wait too long, if nobody speaks up. I'm ok with merging this, but maybe not on a Friday afternoon :)

@steven-johnson
Copy link
Contributor Author

I just landed the change to the buildbots, so it's definitely not gonna get tested anymore. Might as well approve this one too :-)

@shoaibkamil
Copy link
Contributor

Unfortunately LLVM looks like it's failing to build on the buildbots?

@shoaibkamil
Copy link
Contributor

Oh DOH, that's because they were running when you landed the changes to the buildbot config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider dropping MinGW support
3 participants