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
I wanted to make a suggestion regarding the README instructions for building with fpm that might seem evident but I felt that could have avoided me some head scratching.
After forking and downloading the branch locally, the 'git checkout stdlib-fpm' command did not work directly, so I had to do the following which seems a bit more explicit: source ./ci/fpm-deployment.sh cd stdlib-fpm/
I would suggest adding these two lines to the readme but I wanted to ask if there is any reason not to?
(side question: would it be worth it to have a companion fpm-deployment.bat for windows?)
The text was updated successfully, but these errors were encountered:
After forking and downloading the branch locally, the 'git checkout stdlib-fpm' command did not work directly, so I had to do the following which seems a bit more explicit: source ./ci/fpm-deployment.shcd stdlib-fpm/
I would suggest adding these two lines to the readme but I wanted to ask if there is any reason not to?
No, there is nor reason to not mention it. Ideally fpm should support fypp. But meanwhile I support your idea. Would you like to open a PR with your suggestion?
(side question: would it be worth it to have a companion fpm-deployment.bat for windows?)
I am not familiar with Windows. However, if it helpfuls, please propose such a script.
Hello,
I wanted to make a suggestion regarding the README instructions for building with fpm that might seem evident but I felt that could have avoided me some head scratching.
After forking and downloading the branch locally, the 'git checkout stdlib-fpm' command did not work directly, so I had to do the following which seems a bit more explicit:
source ./ci/fpm-deployment.sh
cd stdlib-fpm/
I would suggest adding these two lines to the readme but I wanted to ask if there is any reason not to?
(side question: would it be worth it to have a companion fpm-deployment.bat for windows?)
The text was updated successfully, but these errors were encountered: