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

[C++] Add an auto fallback solution when system Gtest is compiled with a C++ standard lower than 17. #34813

Closed
HaochengLIU opened this issue Mar 31, 2023 · 3 comments · Fixed by #34920

Comments

@HaochengLIU
Copy link
Contributor

Describe the enhancement requested

in PR #34765, Arrow will error out when the detected GTest is compiled with a C++ standard lower than 17. This is a follow-up issue that should support auto fallback:

Proposed solution from @kou :

Add a FindGtestAlt.cmake file (GTestConfig.cmake is a good starting point) and use new target names to refer to suitable Arrow target. See details in this comment

Component(s)

C++

@HaochengLIU
Copy link
Contributor Author

FYI I need to tackle #34565 first in April as it's related to my job. Once it's done I will revisit this enhancement.

@westonpace
Copy link
Member

Do you mean it would fallback to building from source?

@HaochengLIU
Copy link
Contributor Author

yes, the goal is to support automatic fallback

@jorisvandenbossche jorisvandenbossche changed the title [C++] Add an auto fallback solution when system Gtest is cmpiled with a C++ standaard lower than 17. [C++] Add an auto fallback solution when system Gtest is compiled with a C++ standard lower than 17. Apr 4, 2023
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
kou added a commit to kou/arrow that referenced this issue Apr 6, 2023
If incompatible GoogleTest is detected, we can fallback to bundled
GoogleTest automatically.
@kou kou closed this as completed in #34920 Apr 6, 2023
kou added a commit that referenced this issue Apr 6, 2023
### Rationale for this change

#34765 approach has some corner cases. They causes CI failures.

### What changes are included in this PR?

If incompatible GoogleTest is detected, we can fallback to bundled GoogleTest automatically.

### Are these changes tested?

Yes.

### Are there any user-facing changes?

Yes.
* Closes: #34813

Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
@kou kou added this to the 12.0.0 milestone Apr 6, 2023
liujiacheng777 pushed a commit to LoongArch-Python/arrow that referenced this issue May 11, 2023
### Rationale for this change

apache#34765 approach has some corner cases. They causes CI failures.

### What changes are included in this PR?

If incompatible GoogleTest is detected, we can fallback to bundled GoogleTest automatically.

### Are these changes tested?

Yes.

### Are there any user-facing changes?

Yes.
* Closes: apache#34813

Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
ArgusLi pushed a commit to Bit-Quill/arrow that referenced this issue May 15, 2023
### Rationale for this change

apache#34765 approach has some corner cases. They causes CI failures.

### What changes are included in this PR?

If incompatible GoogleTest is detected, we can fallback to bundled GoogleTest automatically.

### Are these changes tested?

Yes.

### Are there any user-facing changes?

Yes.
* Closes: apache#34813

Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
rtpsw pushed a commit to rtpsw/arrow that referenced this issue May 16, 2023
### Rationale for this change

apache#34765 approach has some corner cases. They causes CI failures.

### What changes are included in this PR?

If incompatible GoogleTest is detected, we can fallback to bundled GoogleTest automatically.

### Are these changes tested?

Yes.

### Are there any user-facing changes?

Yes.
* Closes: apache#34813

Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants