I exported a project using Renesas FSP Export -> Export FSP project and exported it as a zip.
When I imported it on to another computer it made a complete shambles of it.
Importing the zip as “import archive” left it as a subdirectory inside another project that it created. One called P003 and one called P003 zip expanded. Needless to say, it could no longer find any references and failed to compile.
Then I extracted the files from the zip and imported using import from file system. That looked OK, and resembled the project that was exported, but also fails to compile with
bsp_cfg,h. - no such file or directory
hal_data.h - no such file or directory
#include hal_data.h is in every other project in the same format, but never gives an error.
What went wrong?
Hello Ian. Can you try to import the exported project zip file by going to "Import -> General -> Existing Projects into Workspace."? That should let you import the project successfully.
-JayeshIf this response, or one provided by another user, answers your question, please verify the answer. Thank you!Renesas Engineering Community Moderatorshttps://community.renesas.com/https://academy.renesas.com/en-support.renesas.com/.../
That’s an improvement! (But how was I to know the difference between “Existing projects into the workspace” and “projects from folder or archive”?)
I’m still left with the “ no such file or directory” for hal_data.h, bsp_clock_cfg.h and bsp_cfg.h
Hang on. . . It came from a machine running Fsp 3.3 and went onto a machine running Fsp 3.6, and if I go into configuration.xml and resave it now compiles.
. . . But it makes me wonder what else might be a problem due to the Fsp being changed. I’m working on a version that doesn’t use FSP which should eliminate that problem.