Closed tdegrunt closed 2 years ago
As these things usually go, I've found a fix. I'm using home-brew's or-tools as mentioned.
export CPLUS_INCLUDE_PATH="/opt/homebrew/include:$CPLUS_INCLUDE_PATH"
bundle config build.or-tools "--with-or-tools-dir=/opt/homebrew/opt/or-tools"
After this a bundle install --redownload
fixed it.
Sidenote: Use a bundle version >= 2.2
Hey @tdegrunt, thanks for sharing! I don't have an ARM Mac to test, but I think it should also be possible to do:
bundle config build.or-tools --with-or-tools-dir=/opt/homebrew
(without CPLUS_INCLUDE_PATH
since it should add /opt/homebrew/include
).
Once a binary installation is available, I'll add it as well. https://github.com/google/or-tools/issues/2893
Perhaps this is the wrong place but I can't get or-tools the run on new hardware.
I've installed or-tools using homebrew:
brew install or-tools
Then in a test folder, I've done:
This all runs fine, but when I try and run a test ruby file:
Any thoughts or pointers?
My arch:
My ruby version: ❯ ruby -v ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [arm64-darwin21]
My /opt/homebrew/opt/or-tools: