topic Create new project in KSDK 2.0 in Kinetis Software Development Kit

Create new project in KSDK 2.0

pietrodicastri — Mon, 16 Mar 2015 12:37:12 GMT

Good morning...

I can import the demos project as explained in some documentation on the web.

But the files are not copied in the project's directory.

I need to create a project in the current working directory with independent files.

So I need a suggestion for how to import a project with all the files copying everything and

dismissing any link with the imported project.

Alternatively I need to import the settings in a totally new project.

Thank You everybody

Pietro

Re: Create new project in KSDK 2.0

ivadorazinova — Mon, 16 Mar 2015 12:51:07 GMT

Hi Pietro,

so do you want to create copy of example and work with this copy?

Best Regards,

Iva

Re: Create new project in KSDK 2.0

ivadorazinova — Mon, 16 Mar 2015 15:28:02 GMT

Pietro di Castri,

please look at the following step-by-step guide. How to create copy of KSDK example in KDS

There is written what you can do if you need the working copy of the KSDK example.

I hope it helps,

Iva

Re: Create new project in KSDK 2.0

dave408 — Thu, 19 Mar 2015 05:39:20 GMT

The step-by-step guide is helpful, but I think only in the case where you just want to create a copy of the KSDK example in the same folder as the rest of the examples. For those that have a different working directory (e.g. something under version control), then I think you have three options:

1. use symbolic links to fake out either KDS or your VCS so that the files can go under version control in your workspace directory, while KDS still thinks all of the relative paths are correct

2. wait for an updated tool like the one Iva has created

3. use a manual process, which takes a bit of time, but will still work. In a nutshell, it involves using the Import feature to import an existing example into your working directory. You'll then need to edit the .project and .cproject files to fix the virtual file pointers and the relative paths to the include folders. I use the ${KSDK_PATH} variable and then do a search and replace on everything that is relative to ${ProjDirPath} so that the include folders can be located by the compiler. The same goes for the linker settings. Generally speaking, once you've done this you can get an example working. It took me a bit of time to figure all of this out, but I have a couple of projects based loosely on demo projects and have them running in a completely separate working directory.