Installing extension for VS code ( CMake, Git, ... )
=> After installing the git extension sign in button is not available like said in the tutorial, one trick is to close vs code and then open it again to have the " clone repository " option available on the main page then by trying to clone the project, the git hub sign in will be prompted. But some students don't have the "clone repository " link. In such case they can't clone ... One trick is to manually clone the project (with another git client like GitHub desktop, or any other method )...
Compiling the initial project
=> The Gcc version available on students' computers is 4.6.1 and not 4.6.0n this confuses them ...
Installing the libraries
=> In the template readme, it is not clear enough how to "install the lib", we should implement the image which shows the desired file tree that is available in the wiki public.
There are also some redundancies with Moodle indications, public project wiki, and template readme. It may be good to choose the exact path the students may follow, start with Moodle telling them the project will be done in a team, and telling them to go to the public project wiki, explaining what is the project and the main mission, then the wiki gives a link to the git template...
Some students had issues with the import issues, they did not get the whole 25 issues ...
(By the way, issues don't start with number 1... but directly start to number 3 )
It may be great to explain that only one student needs to make the import.
It may be great to also explain that it may be useful to delete the build files if files are changed ...
Installing extension for VS code ( CMake, Git, ... ) => After installing the git extension sign in button is not available like said in the tutorial, one trick is to close vs code and then open it again to have the " clone repository " option available on the main page then by trying to clone the project, the git hub sign in will be prompted. But some students don't have the "clone repository " link. In such case they can't clone ... One trick is to manually clone the project (with another git client like GitHub desktop, or any other method )...
Compiling the initial project => The Gcc version available on students' computers is 4.6.1 and not 4.6.0n this confuses them ...
Installing the libraries => In the template readme, it is not clear enough how to "install the lib", we should implement the image which shows the desired file tree that is available in the wiki public.
There are also some redundancies with Moodle indications, public project wiki, and template readme. It may be good to choose the exact path the students may follow, start with Moodle telling them the project will be done in a team, and telling them to go to the public project wiki, explaining what is the project and the main mission, then the wiki gives a link to the git template...
Some students had issues with the import issues, they did not get the whole 25 issues ... (By the way, issues don't start with number 1... but directly start to number 3 ) It may be great to explain that only one student needs to make the import.
It may be great to also explain that it may be useful to delete the build files if files are changed ...