Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] PDE help

Hi,

> Give a detailed description of the steps  
> necessary to debug and deploy an eclipse application (3.5M6) 
> with cdt  
> (M6) with the patches similar to the one described in 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=265483 
> #c2 applied.

Are you on Linux?

this is how I do things on Linux.  There are probably other (maybe
more efficient) ways, based on your particular situation,
but I believe the following generic way will work.

- install eclipse 3.5M6 with nothing else

- run eclipse using
	eclipse  -clean -vm ../../jre1.5.0_13/bin/java -vmargs -Xmx1024M
-XX:PermSize=64M -XX:MaxPermSize=128M -ea

- Check out all CDT plugins using the CVS Repository view
	proxy.eclipse.org:80
	/cvsroot/tools
	checkout everything under HEAD->org.eclipse.cdt->all
	as well as HEAD->org.eclipse.cdt->dsf
	and HEAD->org.eclipse.cdt->dsf-gdb

- all these plugins should build without errors (but lots of warnings)

- apply your patch

- debug as eclipse application

That should do it.

Marc



> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Tobias Hahn
> Sent: Monday, March 30, 2009 11:46 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] PDE help
> 
> Hi all,
> 
> I'd have developed some patches to improve and fix some 
> problems with  
> cdt. However, I'm totally frustrated and about to give up.
> 
> This is what I tried:
> First of all, I imported the plugins I need to patch using PDE and  
> changed the sources I needed. Then I debugged it using Debug As -->  
> Eclipse Application. This used to work perfectly. For some 
> reason, it  
> stopped working and gives me java.lang.OutOfMemoryError: Java heap  
> space when I try to start it. I tried a clean install of eclipse as  
> well as cdt and setting Xmx to anything between 256m and 4g, but no  
> luck.
> 
> Then I tried installing it into the running instance using Export.  
> This had no effect whatsoever.
> 
> Then I increased the qualifier part of the plugin's version and  
> exported it again. This time my patches worked fine (only 
> small local  
> changes), but as a result I'm getting hundreds of NLS missing string  
> errors as well as lots of seemingly related language resource 
> classes  
> not found. To make this super clear: These error occur _only_ 
> with the  
> exported version of the plugin, but _not_ when debugging it using  
> 'Debug As --> Eclipse application'.
> To a certain extend I could live with these -- since I still 
> have hope  
> that there is a path from debugging to deploying.
> 
> So I tried installing these patched plugins on another 
> machine only to  
> find out that there seems to be no method left to install 
> plugins. The  
> Install software wizard will only install features, not single  
> plugins, and just copying them to the plugins or dropins 
> subdirectory  
> of eclipse has no effect whatsoever. Trying to wrap them in a PDE  
> "Feature patch" also has no effect whatsoever.
> 
> Finally I tried to "Import.../Feature", but when I try to 
> deploy it it  
> downloads all plugins from some update site instead of using the  
> patched ones from my workspace.
> 
> I tried to RTFM but the various FAQ I found scattered in the net  
> contradict each other, don't work, obviously refer to ancient 
> versions  
> of eclipse or are clueless themselves (just a quote from the 
> official  
> CDT users faq at http://wiki.eclipse.org/CDT/User/ 
> FAQ#Working_on_the_CDT :
> 
> > How do I distribute my changes to my customers?
> > Anyway that you see fit! Actually, if anybody has suggestions for  
> > this answer, please send them to the cdt-dev mailing list.
> 
> 
> Please, why does it have to be such a pain to develop eclipse???
> 
> So here's my quest(ion): Give a detailed description of the steps  
> necessary to debug and deploy an eclipse application (3.5M6) 
> with cdt  
> (M6) with the patches similar to the one described in 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=265483 
> #c2 applied.
> 
> Any help is appreciated.
> Tobias
> Ableton AG, Sitz: Berlin, Amtsgericht Berlin-Charlottenburg, HRB 72838
> Vorstand: Gerhard Behles, Jan Bohl, Bernd Roggendorf
> Vorsitzender des Aufsichtsrats: Uwe Struck
> 
> 
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 


Back to the top