Attempt at improving BuildInstructions.md



  • Hi,
    I just submitted a pull request to improve BuildInstructions.md a bit and am looking forward to further improvement suggestions. The goal was to make some things more explicit for people trying to get started with building and changing RRF.



  • @oliof Spotted some typos and sent suggestions to your PR.



  • Thanks, committed.



  • btw in the process of setting up new windows build env, and recalled reading this

    dc42 said in Project Dir Visibility Duet3_V06:

    Which version of Eclipse C++ are you using? I recently upgraded to 2020-06.

    I find that some versions of Eclipse occasionally grey out the wrong folder after changing configurations. Changing to a different configuration and back again normally fixes it.

    not sure if that should be reflected in the build instructions or not though


    edit; i also think step12 could perhaps benefit from specifying how to import the project. "File -> Import -> General -> Existing Project into Workspace" as it wasn't immediately clear to me the first time. but i believe it was specified in some version of the instructions.

    screenshots if you feel like adding that, but once what type of import to be used is specified i think that would suffice

    f6946dc8-1c85-4124-a5b6-adc32cfcede8-image.png
    be48aafc-d6fa-4473-87f7-128f7e1a8643-image.png



  • @bearer said in Attempt at improving BuildInstructions.md:

    edit; i also think step12 could perhaps benefit from specifying how to import the project. "File -> Import -> General -> Existing Project into Workspace" as it wasn't immediately clear to me the first time. but i believe it was specified in some version of the instructions.

    Even shorter is

    File -> Open Projects from File System...

    as all of these GitHub repositories are already eclipse projects.


Log in to reply