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
{{ message }}
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.
We should have a standard lookup paths to load configuration files from, such as the name of the current application (binary or the FBP name if using sol-fbp-runner or sol-fbp-generator), as well as use the board name as in sol_platform_get_board_name().
An idea is the following (from highest to lowest priority):
envvar $SOL_FLOW_MODULE_RESOLVER_CONFFILE
./sol-flow-$APPNAME-$BOARD_NAME.json
$PKGSYSCONFDIR/sol-flow-$APPNAME-$BOARD_NAME.json
./sol-flow-$APPNAME.json
$PKGSYSCONFDIR/sol-flow-$APPNAME.json
./sol-flow.json
$PKGSYSCONFDIR/sol-flow.json
Please add proper SOL_DBG() before trying to load each component so it's easy to debug which file is being used and those that failed (didn't exist or failed to load).
The text was updated successfully, but these errors were encountered:
We should have a standard lookup paths to load configuration files from, such as the name of the current application (binary or the FBP name if using
sol-fbp-runner
orsol-fbp-generator
), as well as use the board name as insol_platform_get_board_name()
.An idea is the following (from highest to lowest priority):
$SOL_FLOW_MODULE_RESOLVER_CONFFILE
./sol-flow-$APPNAME-$BOARD_NAME.json
$PKGSYSCONFDIR/sol-flow-$APPNAME-$BOARD_NAME.json
./sol-flow-$APPNAME.json
$PKGSYSCONFDIR/sol-flow-$APPNAME.json
./sol-flow.json
$PKGSYSCONFDIR/sol-flow.json
Please add proper
SOL_DBG()
before trying to load each component so it's easy to debug which file is being used and those that failed (didn't exist or failed to load).The text was updated successfully, but these errors were encountered: