Update/Synch of project during generation of PE code fails if source files are ("heavily") linked

[björnhammarberg]

In our product, we like to include the KSDK within the product folder for archiving/completion reasons. (To avoid confusion of which version is actually part of the build some five years down the line...)

With linking and version control it is possible to "include" the code without creating multiple copies of the same source components.

With Code Warrior, this was working like a charm but with KDS it doesn't work as smoothly.

The setup is like this:

* Product folder contains a KSDK folder anda KSDK_BUILD folder. The KSDK project for a particular board is kept within a KSDK_BUILD/mqx_frdmk22f folder.

* SDK path is set to ${ProjDirPath}/../../KSDK (To create the project, an absolute path must be given during creation and later changed to the relative path.)

* The project is created with linking to the KSDK. (Since the project was created using an absolute path, it must be changed manually to a relative path for all linked files.)

The problems are:

* A relative path is not possible to use when creating the Kinetis project

* During creation an absolute path must first be used and later changing this manually in the .project file and the PE settings

* After PE generation, there are a 100 or so errors complaining about missing links and such; they disappear by closing and opening the project.

* After re-opening the project, there are a few errors left concerning the newly added files as a result of adding a component in PE. These files were not added and must be linked manually.

* After adding the links, the Problems view still show the errors and the only(?) way to get rid of them is by selecting and deleting them in the view.

Would it be possible to get this kind of support in an KDS update soon? (As I said, all of this worked like a charm in Code Warrior.)

[Carlos_Mendoza]

Hi Bjorn,

Please see my comments regarding your problems:

1.- Currently KDS New Project Wizard does not support relative paths to indicate the SDK Location, I will send your feedback about this to the KDS development team.

2.- There is no need to manually modify the absolute path on the .project file, you can do this on the project properties by going to C/C++ Build > Build Variables and editing the PROJECT_KSDK_PATH build variable:

After changing the PROJECT_KSDK_PATH build variable and applying the changes you will see that the SDK path is also updated on the Processor Expert settings:

3 and 4.- I have run some test and did not get any errors after changing the SDK path following the steps above, can you try it and let me know if you still get the errors while generating the PEx code?

5.- Please try making a Clean to your project, this will make those errors disappear from the Problems view and should no longer appear after building the project again.

Hope it helps!

Best Regards,

Carlos Mendoza

Technical Support Engineer

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------