I have installed SDK 3.0 and KSDK 1.2.0
If I try to import an example project without coping it to the workspace all seems to be ok.
If I set copy to the workspace I have a lot of errors as seen in the attached screen.
1 ) Please checked "Include paths" here :
2) Please do like this then show more error information to us :
3) You can also do like this :
Firstly copy the project to the workspace , then open the KDS use this workspace ,then import your project , build . I'm waiting your result after your try this method.
Have a great day,
Alice
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
The included paths are as shown on the attached jpeg
I have copied the content of the folder c:\Freescale\KDS_1.2.0\example\frdm64f\demo_apps\dac_adc_demo\kds
to a folder dac_adc_demo in workspace.kds, start KDS and imported the project from workspace.kds.
It does not work.
Hello PierGiovanni Gordini:
Just as Erich Styger explains, you cannot move the project from its original location because of the relative paths to the linked files.
If you need a copy of the project to make changes, an easier approach is by following the document in the next link, but still the cloned project must be placed in the same folder:
How to create copy of KSDK example in KDS
Regards!,
Jorge Gonzalez
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
If you *copy* the project, then all the project relative paths like ../../../../platform... will likely not work.
The SDK projects are setup in such a way that they need to 'stay in place' inside the SDK. Otherwise you need to adapt the compiler include paths accordingly.
Keep in mind that the relative paths like ../../../... are based on the output (usually named 'Debug') folder of your project.
I hope this helps,
Erich