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
Can the swan-provider work with a "normal" boost, not some separate copy, which is mentioned in the instructions (Step 8,9 - boostd --boost-repo=$SWAN_PATH/provider/boost net ... )?
I mean If the boost is already installed in it's own repo, why should we move it to $SWAN_PATH?
Why not make the swan provider just use the already installed and initialized boostd? After all, all the environment variables necessary for this can be set quickly and simply, without any movement of folders and repositories.
The text was updated successfully, but these errors were encountered:
Can the swan-provider work with a "normal"
boost
, not some separate copy, which is mentioned in the instructions (Step 8,9 -boostd --boost-repo=$SWAN_PATH/provider/boost net ...
)?I mean If the
boost
is already installed in it's own repo, why should we move it to$SWAN_PATH
?Why not make the swan provider just use the already installed and initialized boostd? After all, all the environment variables necessary for this can be set quickly and simply, without any movement of folders and repositories.
The text was updated successfully, but these errors were encountered: