You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
odb depends on libodb (no option needed), so installing odb will first install libodb without option (linked to the default C++ standard library depending on your OS X version).
Let's take libodb-sqlite: It depends on libodb but specifying a build option. Depending on something already installed with a different build option results in reinstalling it with the specified options.
To summarize, if you want to install odb and it's libodbs, you need to specify libodb at first and the right build option at the end, to make sure homebrew will install libodb once with the right options.
Example, you want to install odb + libodb-sqlite and use the Apple's libstdc++. If you do this:
% brew install odb libodb-sqlite --with-libstdc++
You'll see libodb installing because it's an odb dependency, then odb, then libodb again because build options are specified by libodb-sqlite (taken from the command line --with-* option)
odb
depends onlibodb
(no option needed), so installingodb
will first installlibodb
without option (linked to the default C++ standard library depending on your OS X version).Let's take
libodb-sqlite
: It depends onlibodb
but specifying a build option. Depending on something already installed with a different build option results in reinstalling it with the specified options.To summarize, if you want to install
odb
and it'slibodb
s, you need to specifylibodb
at first and the right build option at the end, to make sure homebrew will installlibodb
once with the right options.Example, you want to install
odb
+libodb-sqlite
and use the Apple'slibstdc++
. If you do this:You'll see
libodb
installing because it's anodb
dependency, thenodb
, thenlibodb
again because build options are specified bylibodb-sqlite
(taken from the command line--with-*
option)For now, you should do:
The text was updated successfully, but these errors were encountered: