Project was not created correctly. No Zephyr build configuration in project.

[novalisek]

Hi, I am having problem compiling project created by older version of the plugin. I am getting "Project was not created correctly. No Zephyr build configuration in project." I am using eclipse 2020-09

So I created new project by new project wizzard with new plugin and checked what is different and I think there are no changes except project name.

Anyway, the easiest way to reproduce is

• create new workspace1

• create new example application test1

• compiles without problem

• create new workspace2

• import test1 from workspace1 (doesn't matter if "copy projects into workspace" is selected or not)

• doesnt't compile with "Project was not created correctly. No Zephyr build configuration in project."

What is the plugin searching for to indicate. that there is no zephyr build configuration in project? Are there any files stored outside of project, which include which projects were created by the plugin?

Thanks.

[novalisek]

Just to let you know, what helped to me:

I copied workspace1\.metadata\.plugins\org.eclipse.core.resources\.projects\test01\.location to workspace2\.metadata\.plugins\org.eclipse.core.resources\.projects\test01\.location

and compilation also works in new workspace2

I think this should be automated somehow, when copying/importing project (if Eclipse supports it) ... or have some button "make zephyr project from selected project" so that it adds all necessary info to the project/workspace so that it compiles without problem.

[dcpleung]

Do you remember which old version of plugin you used? If it is before 2019-12, the issue is expected due to changes in CDT (see #23).

As for importing the project, it does not work at all due to how CDT stores build configurations and project related information. There are internal CDT classes for accessing them but this plugin cannot access those classes. The workaround is to create an empty project and copy the source files over (actual copy not linked resources).

[novalisek]

Yes the version was older, before 2019-12, so that was the first problem why I couldn't open it directly, second was that I tried to import it. May be there should be at least some note about this "import" problem and it's workaround if it cannot be fixed.