Community
Participate
Working Groups
Although it probably has nothing to do with the exact environment, I will list it anyway to aid in duplicating and verifying the issue. Using Kinetis Design Studio, importing a (linked) project when the Copy Project to Workspace checkbox is enabled, does not work. The include paths resolve incorrectly, causing a linked project that would compile successfully, if imported without the copy to workspace enabled, to instead be uncompilable because of unresolvable file paths. It appears as if path variables are not inherited from the workspace (or current running environment) so that the imported paths are incorrectly resolved. This makes it impossible to create a stand-alone project from a template project. The copy feature of the import wizard should correctly resolve all links so that a linked template project becomes a stand-alone, project, that could, in its entirety be then checked into a version control system.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
