What's supposed to happen (if following the official setup steps) is that the first time Eclipse builds the project, it looks at the compiler command line arguments (which includes lots of "-I" arguments passing header search paths). However that's what a lot of people have used in order to get things working. You're correct that we don't recommend or require any manual setting of include paths. I suspect that if I had followed the formal documentation from the outset step by step, all would have been well. It is the last step in the formal docs that I had missed in my recipe practice which, once done, has resulted in it working for me. it is just the recipe that I am following. To be clear, I sure am not saying that my recipe is any better. I do not believe that is the recipe supplied in the formal docs. Now I "fix up" the existent C/C++ project by importing the include paths necessary. In Eclipse Create a new C or C++ makefile project and point the Project folder to the existent folder created by the GIT clone In the workspace folder, clone the ESP-IDF template project into a folder with the name of the project I want to buildģ. Create a Workspace folder (if one doesn't already exist)Ģ. The end result in Eclipse is that we have a workspace and in the workspace we have projects and in the projects we have control files. However, in Eclipse, there are many ways to "skin the cat". No question that the instructions in the formal docs gave me the notion of where to start looking.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |