I want to migrate the project in atmel-studio from eclipse cdt, as I started working on an embedded c/c++ project I understood that atmel-ice is not debugging properly in eclipse it's just helping me to flash firmware nothing more than that. So, Want to migrate my whole project to atmel-studio. So, I could debug it. Looking for help thanks.
As an option, look into the atmel-studio capability of debugging an externally produced elf. The tools I've used (keil, tensilica, IAR) all had ways to make a project that could debug an elf file produced externally. You may lose some magic like source parsing/intellisense or whatever, but I've found source line debugging works just fine.
I've never used Atmel Studio, but in searching the web, I found:
http://ww1.microchip.com/downloads/en/devicedoc/atmel-42167-atmel-studio_user%20guide.pdf
http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-ECD8A826-B1DA-44FC-BE0B-5A53418A47BD-en-US-5/index.html?GUID-4C53CCC3-659D-4030-A7FD-566B19C87747
Both of which say "File->Open Object file for debugging"
Related
I am trying to learn about native Android, using NDK.
I find some sample projects in NDK folder and on the Internet. After much configuration, they are runnable.
But, my problem is: when I open a .c or .h file in JNI folder with Eclipse (just want to see what it is), Eclipse shows many error in this file. For example, it don't know what is JNIEnv, jobject, jstring.
I haven't made any change in the project, just opening it. Errors mean I can't rerun it again except if I delete it from the workspace then reimport it.
Eclipse does not work well with C/C++ files. At least, for me it did not.
After some search, I have managed to configure Code::Blocks to support NDK, please see this answer to the question:
Need a simple Linux C++ IDE (Android NDK) .
I'm using Intellij IDEA/Android Studio.
I was asked not to make any commits unless my code doesn't trigger any warnings in Problems View of Eclipse IDE.
So, is there any quick way to port Eclipse's analysis configuration to IDEA?
Thanks.
There is not. There is the Eclipse Code Formatter third party plug-in for portng over code formatting definitions. Pehaps you can contact that developer and see if he would add problems/inspections definition syncing. Until then, I see two options for you...
Configure your IDEA inspections so they match the team's Eclipse settings. This of course would require some time to initially set up. But I think in the end, it's the best solution.
IDEA can export to files in eclipse format. As part of that it can keep its configuration linked to the eclipse files. This way you could pop over to eclipse to check for problems prior to committing.
I'm a Visual Studio .NET developer who's trying to switch to Eclipse/SpringSource Tool Suite, so I get stuck on probably simple problems. Please bear with me.
I'm working on a Spring MVC project associated with an Apache Tomcat server. If I right-click the server and choose Start (alternatively Package Explorer->right-click project->Run As->Run on Server), my project is compiled and started. Compiler output is shown in Console window. Fine.
But if I simply want to compile the project without running it, I try selecting Project->Build All, Project->Build Project, or Project->Build Working Set. Nothing happens, no screen output, nothing -- despite having non-compiling code.
I expected to see the compiler errors on screen, preferably with the errors highlighted in the code. For what it's worth, I have deselected Project->Build Automatically. Anybody knows what I should do?
Eclipse and STS use incremental compilation. So, every time a file is saved, it is automatically compiled (as well as all files dependent on it). When you deselect Build Automatically, then yes, you will need to explicitly build, but this will still be an incremental build (ie- only the changed files and dependencies).
See here for a bit of a discussion on how incremental building works in Eclipse: http://www.eclipse.org/articles/Article-Builders/builders.html
I have an Eclipse project I've been working on for some time now, and I'd like to open source it. But to do that I'd like to have a clean Makefile like the majority of other open source programs. I understand I could make my own, but it would be better if Eclipse could manage it for me. Getting Eclipse to generate a CMake file would be even better, but I can settle for a plain makefile if that is easiest. So, how can I get Eclipse to do this? There are a few posts on the internet that suggest selecting "Managed make" when creating a project, but they were from a few years ago and are outdated. When I try to create a C project, there is the option to create a "Makefile project", but it creates the makefile in a folder called "Linux GCC" and makes everything cluttered. Any suggestions?
I've been a *nix guy for 25+ years and am a big fan of make. However, making your Eclipse project dependent upon make is going to exclude the Mac and Windows community. Why don't you just export the Eclipse project and open source it as an Eclipse project? Then users can can have it ready to extend if they choose. You didn't specify the language your project is written in, if it's Java (pretty common for Eclipse) why not create an ant build file for the project?
Just a thought.
I ended up just creating a CMake project by hand. CMake files are really not that hard to make, and it's a lot easier than trying to get Eclipse to do it for you. Plus, they're cross-platform.
Would a CMakeBuilder eclipse plugin, associated with this tutorial be a good fit for what you are trying to do?
The end result would be something like:
(source: vtk.org)
If you've been building your project using the Debug configuration the makefile Eclipse generates is stored in the Debug folder of your project (or the Release folder if you've built it using the release configuration).
I've downloaded C/C++ libraries from Cygwin, and set the environment variables according to the instructions here, in NetBeans.
I've also gone through this.
Actually I followed the same steps on a different machine and everything worked out fine.
But on my machine the associations aren't made.
for example: #include<stdio.h> says No such file or directory.
Any idea what the problem might be?
The Cygwin package I downloaded is also fine, I downloaded it twice.
If it's complaining about a #include, that's a compile issue, not a linking issue.
What happens if you create a new C/C++ application project and try to build it?
In the Build node of the project properties, is the correct Tool Collection selected? (Cygwin in your case). And the Tools -> Options, on the C/C++ tab, is that tool collection set up correctly?
You should check whether you have a file c:\cygwin\usr\include\stdio.h.