I have stuck with problem of building Qt projects in Eclipse. First of all here is the sequence of steps which I went through when I installed Qt plugin.
I develop in Eclipse for Java Developers, so firstly I downloaded CDT plugin for eclipse, using Install Wizard.
Then I downloaded and install latest Qt SDK with all libraries, including libraries for mobile developement.
The next step was downloading and setting up Qt plugin for Eclipse.
After I have done everything, I began to configure Eclipse for work with CDT and Qt.
1) I pointed in Windows->Preferences->Qt this attributes:
[Name: Qt4.7.3]
[BinPath: C:\QtSDK\Desktop\Qt\4.7.3\mingw\bin]
[IncludePath: C:\QtSDK\Desktop\Qt\4.7.3\mingw\include]
2) I changed Windows->Preferences->C/C++->New CDT Project Wizard->Makefile Project->Builder Settings->Build Command to mingw32-make, because it tried to launch make instead and of course projects didn't build.
Everything works fine but everytime when I create new Qt or C/C++ Project I have to modify it's Builder settings properties and MakeTarget properties, renaming build commands to mingw32-make. Moreover when I save project, Eclipse should rebuild it, but I get nothing and have to build it manually, using MakeTarget->Build in debug mode.
Tell me please what did I miss during configuration.
Related
I need to use Eclipse and Android Studio on the same computer, simultaneously, for different projects.
The Eclipse project is Enterprise Java deploying on Payara (Glassfish) via the WTP toolkit and Deployment Assembly. When setting up the project I build with gradle build and gradle eclipse, which pulls all the required dependencies and configures the Deployment Assembly in Eclipse. However, I believe that any incremental code changes thereafter are compiled by Eclipse without using gradle (e.g., when I save a file).
Android Studio always compiles with gradle.
The issue that I have is that every couple of weeks, when I compile my Android Studio project, gradle decides to delete all my Eclipse project dependencies. My guess is that it thinks that they are not in use any more, since Eclipse compiles outside gradle. This results in my Eclipse workspace pointing to libs that are no longer there.
If I manually run gradle build in my Eclipse project dir, my dependencies are restored and Eclipse no longer complains. But something seems to be cached wrong somewhere so after this my web app will no longer deploy on the server. At that point my workspace is effectively corrupted and to this day I haven't found any workaround, other than to delete it and start all over again. Which is *A LOT* of work to reconfigure.
Any help will be greatly appreciated.
I am currently working on eclipse plug-in that involves many modules, and I would like to debug and run this eclipse plug-in from IntelliJ.I open this project in IntelliJ to edit code but when I have to run/debug this project I have to open eclipse IDE and start it from there. How can I use IntelliJ to do this?
I haven't actually tried this ... but you could try launching the RCP application stand alone but with the remote debug parameters specified for in your application's .ini file.
Then just point IntelliJ to the appropriate source and attach it's debugger to the running app.
Why do you want to do that? Eclipse has multiple tools for the plugin development that you will miss in IntelliJ. Also you need to build your plugin as product headless and then attach a debugger to it.
In my opinion it doesn't worth the effort. I would install Eclipse and devolop with eclipse.
I checked in eclipse/java plugin project from svn repository.
Eclipse automatically builds the code to show hundreds of errors.
It seems like that eclipse doesn't properly link to the plugin libraries. Googling to find this site that I need dependencies and other tabs in plugin.xml.
What might be wrong? I use Indogo(3.7) on Mac OS X 10.7.4
I used Indigo (3.7) for my Mac, but it happened so that the plugin was built on Helios (3.6). When I run the plugin using Helios, I got the project compiled without errors.
It seems like that some of the plugins are (heavily) version dependent.
Looks like you got the base XML editor instead of the plugin.xml editor.
This is probably caused by your not having the eclipse plugin development environment (PDE) enabled in a new workspace.
Try creating a new plugin project (this will enable the necessary plugin tools), or go to the preferences and enable the "correct" capability. Since the capabilities seem to change from release to release, I always use the first method and then delete the new project.
I have installed cdt-master-6.0.2.zip (link) to my Eclipse by extracting it to the Eclipse installation dir. I'm using Eclipse 3.5 in Windows 7 x86 machine. But the plugin doesn't show up when I start Eclipse (I can't create a new cpp project). Yet cdt shows up in Help > About Eclipse SDK > About Eclipse SDK Features. What am I missing here?
To install plug-ins into Eclipse you should always prefer using the user interface through Help > Install new software menu.
Anyway if you really want to install plug-ins manually into your Eclipse installation, you have to place them into the dropins folder.
BUT this way you will have to resolve plug-in dependencies by yourself. If all dependencies are not satifsied, the concerned plug-ins will fail to start silently. This is why you should REALLY prefer to use the standard plug-in installation method to avoid any problem.
I have implemented a graph editor with Eclipse EMF and GMF frameworks. After completing my project, I realized that this plugin shows dependencies (not explicitly added by me) on some OS-specific plugins.i.e:org.eclipse.ui.win32, org.eclipse.swt.win32.win32.x86. And whenever I have tried to bypass this dependency at my update site something went wrong with the installation process of the plugin.
As such it is impossible to run my plugin in *nix environment or even win64 machines.This seems a very heavy constraint dependency to me. Am I doing something in a wrong way? Or is there no other way of building Eclipse plugins which are cross-platform other than building the project from scratch at each different OSs?
We created a similar style of plug-in in my project. Under "Plug-in Dependencies" in Package Explorer I can see org.eclipse.swt.win32 listed, but it is not listed in required plug-ins in plugin.xml.
We also successfully created an update site which works for Mac users without issue.
So, yes it is possible to have a cross-platform plug-in.
I would suggest you first try to to use "Export..." -> "Deployable plug-ins and fragments" to create a bunch of jar files for your plug-in. See if these can be successfully installed by copying into the drop-ins folder of a fresh eclipse installation. Do this first on a Win32 install, then try on another platform. Once you have that working, use the new Eclipse installation to create the Update site.