|
|
|
| Re: branding win32/linux rcp using ant [message #652436 is a reply to message #652250] |
Thu, 03 February 2011 22:01   |
|
Hello
It is possible to brand a win32/linux rcp application using ant. It is better to do this at the beginning because it is easier to debug build problems. When you have an rcp application with multiple plugins it is sometimes very hard to debug. More over sometimes the PDE error messages are not very clear.
Do you have an product configuration based on plugins or features? I assume that it is a plugins based one.
In your actual situation:
1. Just try to use only a single config like 'win32, win32, x86' to see if you still have the problem.
2. Then you should check your product/feature definition (to see if you do not have the .aix. referenced there). Put in your product definition only the necessary plug-ins.
3. As debug procedure: remove all plugins from your product definition and then add the plugins one by one to the product definition (from your launch configuration). Every time you add a plugin you create the build and see if still works.
4. Or you can create a product configuration from an working launch configuration and use this product configuration in the build.
Remember that for multiple configurations you need the delta pack.
In the future you can try the step-by-step approach:
1. Start from a single plugin.
2. Create the ant build using a single config like 'win32, win32, x86' and see if it works.
3. If you are using the headless PDE build with ant then you can integrate the build with a continuous integration tool like Hudson/CruiseControl. This way when you make a change to your application you can quickly see what made the build to fail.
Time is what you make of it.
|
|
|
|
|
|
|
| Re: branding win32/linux rcp using ant [message #653469 is a reply to message #653323] |
Wed, 09 February 2011 20:47 |
|
Hello
1. No exe generated could come from some different points:
a) One is the missing delta pack; (most likely from my point if view)
b) in your product definition you did not checked the 'This product includes native launcher artifacts' checkbox.
2. "org.eclipse.equinox.executable" is in the delta pack (delta pack was pointed both by me and in the article by Andrew Niefer). See http://aniefer.blogspot.com/2009/06/using-deltapack-in-eclip se-35.html for delta pack information.
But if Buckminster is working for you and you do not have any kind of restriction in using it, then go ahead with.
I do not read anything about a 'common approach' when it comes to building RCP applications. Everybody uses the solution that works in his/her environment (Buckminster, Tycho, PDE headless build, PDE Export from IDE).
P.S. I did not used Buckminster so I cannot tell why it works in your case.
Time is what you make of it.
|
|
|
Powered by
FUDForum. Page generated in 0.02067 seconds
] 
Search
Help
Register
Login
Home
