ORC-1936: Get build and example dir from build system rather than gtest

[WillAyd]

What changes were proposed in this pull request?

Rather than pulling the build and example directory from gtest arguments, this pulls it from the build system.

Why are the changes needed?

When orc is used as a subproject, the current method of grabbing the arguments from the build system fails

How was this patch tested?

Tests were run locally

Was this patch authored or co-authored using generative AI tooling?

No

[dongjoon-hyun]

Could you make CIs happy, @WillAyd ?

[WillAyd]

Sorry about the delay - all green!

[dongjoon-hyun]

+1, LGTM. Thank you, @WillAyd .
Merged to main for Apache ORC 2.2.0.

[dongjoon-hyun]

Oh my. ORC-2238 doesn't exist, @WillAyd . I'll reset this commit first.

Please don't do like this again. As you know, Apache repository uses ORC-XXX as a hyperlink pattern for the JIRA system.

[dongjoon-hyun]

This is removed from master branch due to the invalid ORC JIRA ID.

[WillAyd]

Ah sorry - I used the issue number which is 2238. Where can I find the Jira number?

[dongjoon-hyun]

Here is the Apache ORC developer guideline.

https://orc.apache.org/develop/

Each code change requires a jira to track the discussion of the change.

In addition, it seems that you missed my previous comment here.

• ORC-1906: Support Meson build #2249 (comment)

[WillAyd]

OK great. I'll open a Jira ticket to track the github issue then. Should we reopen and update the title of this PR after that or should I create a new PR entirely?

Thanks for the patience - every project is a little different so its a challenge to keep track of all of their requirements :-)

[WillAyd]

https://issues.apache.org/jira/browse/ORC-1936 has been opened

[dongjoon-hyun]

Thank you. I reopened this PR with your new JIRA ID, ORC-1936 .

[dongjoon-hyun]

After passing CI agains, I will put it back to main branch again.

[dongjoon-hyun]

Merged to the main branch again.