-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove RTE nature from the project #17
Comments
What would be the benefit of that? Why is RTE a problem for you? |
For example use case: I want to share my Eclipse project to my colleague, that does not have RTE package installed. He will not modify RTE configuration, only compile and debug, so he does not need RTE. What I see as an problem, I did a legal Eclipse operation (file deletition), and ARM Eclipse plugin throws an exception during re-opening the project. |
thanks, we will look into it. |
The problem here is that an RTE project is dynamic and refers to location where packs are installed:
Just removing the RTE nature will not solve the problem. Some kind of an export procedure is required to store all required information locally and update build settings accordingly. As far as deletion of an .rteconfig is concerned it is inline with Eclipse practice:
|
For dynamic linking - would it be possible to create standalone project without external dependency (e.g. copy all files into Eclipse project)? This would be useful feature for sure.
|
It would be nice to be able to remove RTE nature from the Eclipse project.
I have removed {project}.rteconfig file using Delete command from popup menu (in Eclipse Project Explorer) and now if I open the project, the following exception is thrown:
The text was updated successfully, but these errors were encountered: