Community
Participate
Working Groups
I am using the PDE product export wizard from the product definition editor to produce builds of an Eclipse-based app. Unfortunately the final build for mac os x cocoa-64 doesn't look very good. The product zip file is produced nicely, but the app fails to open when clicking on the generated native launcher. This works nicely in 3.6m6, but fails from 3.6m7 until 3.6rc3. Interestingly the app icon for the native launcher is missing as well.
To be more exact on this: The generated app is missing the pinfo file and the unix executable.
Do you have the deltapack in your target? (or more specifically, org.eclipse.equinox.executable?) Are you exporting with "Generate metadata repository" turned on? My first thought is that perhaps the director install which happens at the end of a p2 export is encountering a problem and the error is not getting reported in the UI. This would result in a incomplete product (ie missing the executable). If you are exporting with metadata, one way to check this would be to do a manual install using the resulting repository. This can be done using the p2 director application on the command line: eclipse -application org.eclipse.equinox.p2.director -repository file:/exported/repository -installIU com.your.product.id -profile Profile -profileProperties org.eclipse.update.install.features=true -destination /tmp/eclipse/ -bundlepool /tmp/eclipse/ -p2.os macosx -p2.ws cocoa -p2.arch x86_64 -roaming
I have the delta pack installed, including the feature org.eclipse.equinox.executable. And I am *not* generating a metadata repository (don't need a repo at the moment).
I have not been able to reproduce this on macosx.cocoa.x86 Would it be possible to attach a sample project that causes this? I tried the hello world rcp app, based on both plugins and features. Export works for the default platform (x86, not selecting multiple platforms). When I select Export for multiple platforms and include x86_64, that seems to work as well (though I can run it because this isn't a 64 bit machine, all the files are there as expected). I added the deltapack to my target by editing the "Running Platform (Active)" and adding the folder where I extracted the deltapack (separate from my install).
Och, seems to be the typical "stupid-user" problem ;-) I need to check "include native launcher artifacts" at the product configuration editor. Seems like this is new or Eclipse lost this setting when switching between the different versions. Nevertheless, works now fine! Sorry for the trouble!!!
See bug 291507, that option never actually worked before. That bug is now fixed, so it could be you've had the box unchecked and it just never actually affected anything before?
Yepp, sounds exactly what I experienced. Thanks a lot for your help and time!!!
(In reply to comment #6) > See bug 291507, that option never actually worked before. That bug is now > fixed, so it could be you've had the box unchecked and it just never actually > affected anything before? I was experiencing this problem, after reading this tkt I checked the box and it started working fine from the IDE. However, when I run a headless build using the same product file and the scripts in org.eclipse.pde.build, I still get the same problem (no executable). My headless build worked fine with 3.5.2 and now I'm trying to update to 3.6. Is there anything else that needs to be set for a headless build? thanks!
