Home » Newcomers » Newcomers » Using a project template, then putting it into source control(I've used a project template to begin a Kinetis application. Putting the modified project into source control has proved difficult due to virtual folders and links.)
| Using a project template, then putting it into source control [message #1728282] |
Fri, 01 April 2016 11:31  |
Eclipse User |
|
|
|
I began a Kinetis boot loader project using the template provided by NXP/Freescale. After modifications to suit our application, I wanted to put the code into a version control system. However, the project import utility does not allow a linked template to be imported with the Preferences->General->Workspace->Enable linked resources choice disabled. I tried to archive the project (which has virtual folders) but the archive appeared to preserve rather than resolve the links. Is it possible to have a self contained project for revision control check-in? Clearly, the initial check-in of code has to be all inclusive.
How can one resolve all of the links in a project without manually going through the complete project? I must have missed something, otherwise using Eclipse with SVN would be very difficult.
|
|
| |
| Re: Using a project template, then putting it into source control [message #1728303 is a reply to message #1728297] |
Fri, 01 April 2016 13:43  |
| Eclipse User |
|
|
|
Actually, getting the Kinetis SDK and boot loader is a bit involved and is only applicable to that platform. I think you'd need to have registered with NXP to download the SDK. http://kex.freescale.com/en/summary?cas_auth=1
The boot loader is at: http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/kinetis-cortex-m-mcus/kinetis-symbols-footprints-and-models/kinetis-bootloader:KBOOT
However, the key element is as you pointed out, the projects all include links. To write code for a particular development card, in my case the Tower TWR-K65F180M, one chooses a project template from many, many templates available in the SDK. When the project is imported into Kinetis Development Studio, virtual links are generated to SDK files that are applicable for a particular processor and development board. Therein lies the problem. That is the starting place for a project. Now, after customizing that template, I'd like to check that source tree into subversion, but the tree doesn't exist as such, it is a combination of links and actual files.
It would be nice to be able to resolve all of the links so that they reside on disk, in the source tree and so, can be checked into a revision control system. In general, I understand the motivation for virtual folders and files in Eclipse, but I am a bit surprised that there isn't an obvious way to resolve the links so that a real source tree can be created.
|
|
| |
| Re: Using a project template, then putting it into source control [message #1728306 is a reply to message #1728305] |
Fri, 01 April 2016 14:24 |
| Eclipse User |
|
|
|
I can resolve them manually and did. It just seemed that there should have been a way to do it automatically. Again, I agree with the sentiment of links, but why should one put all of the code to support every Kinetis processor and development card into version control, when using a project template as a starting point? That's what it would take to use links in this case. While I can agree that there are very good reasons to use virtual folders in a build tree, there are also very good reasons not to.
In the case of NXP and the Kinetis design environment, the SDK being made up of many projects using virtual links to files saves space and reduces the complexity of supporting the SDK. However, once a developer has created a project that only requires 2% of the SDK, putting the complete SDK under version control to preserve the virtual links no longer makes sense, in my opinion. In that case having a way to import a project and create a non-virtual source tree would be more appropriate.
I'm a novice when it comes to Eclipse, only having used it sporadically through the years. I know there are hooks for some version control systems, but I didn't see one in my current IDE for Subversion, which is what we are using.
[Updated on: Fri, 01 April 2016 14:27] by Moderator |
|
| |
| Re: Using a project template, then putting it into source control [message #1728308 is a reply to message #1728307] |
Fri, 01 April 2016 14:57 |
| Eclipse User |
|
|
|
I'm still not understanding why you want to produce a self-contained project that does not link to the SDK. IF the SDK is required, generally, to do development on this platform, wouldn't you expect every developer to have the SDK and thus be able to import the project with links? As an example, that's how the Android Development Tools worked - there were Eclipse plug-ins and then there was the Android SDK, the two were separate but the Eclipse plug-ins know how to use the SDK appropriately and just did not work without it.
In any case, that's a feature that I would expect the SDK and customized-Eclipse-package to provide, not Eclipse directly. Like I said, outside the narrow context in which you're working, linked resources are somewhat rare and when needed they don't have a need to convert themselves to in-project contents.
It sounds like a nice feature to request of this Kinetis Development Studio, however
[Updated on: Fri, 01 April 2016 15:00] by Moderator |
|
| | |
Goto Forum:
Current Time: Thu Jul 24 19:45:10 EDT 2025
Powered by FUDForum. Page generated in 0.10147 seconds |
Home