-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Mac OS X builds should ignore the Homebrew-installed CryptoPP #3493
Comments
So it pulls headers from homebrew cryptopp? |
@chfast Yes, it pulls headers from homebrew cryptopp. After adding
|
No need to check, version 565 means you are taking headers from homebrew (our local one is 566). |
What you can do is:
Show me 2. and 3. |
|
|
Sorry to interject again. The Cmake Xcode generator is broken. It does not copy I believe the same problem occurs with It may explain why you are linking against the wrong version of the library. Also see Cmake generated Xcode project does not produce library artifacts? on Stack Overflow. And see Issue 355 in the Crypto++ bug tracker. |
I think the issue on MacOS is because of this CMake config: https://github.com/ethereum/cpp-ethereum/pull/3518/files#diff-2e108b1166cce4167a2464426d9f93ceL176 (should go away with this PR). |
Even on
|
Its a bit misleading. You could be linking against a shared object version 5.5, but if library versions are mixed/matched, then you will get 5.6.5 from the header. What do you suggest for stashing away the build number version? Do you want a function like |
The main issue is that our build configuration puts |
That directory is Homebrew's default installation target. |
Otherwise problems like #3492 (crash) and #3465 (hash mismatch) happen.
The text was updated successfully, but these errors were encountered: