[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] org.eclipse.jdt.launcing.macosx & the Mac build
|
Dean,
The launch configs are provided by JDT/Debug. So I guess you'll get better
feedback if you post to jdt-debug-dev...
Jerome
|---------+------------------------------>
| | "Dean Roberts" |
| | <Dean_Roberts@oti.c|
| | om> |
| | Sent by: |
| | jdt-core-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 09/12/2002 05:14 PM|
| | Please respond to |
| | jdt-core-dev |
| | |
|---------+------------------------------>
>--------------------------------------------------------------------------------------------------------------------|
| |
| To: jdt-core-dev@xxxxxxxxxxx, platform-swt-dev@xxxxxxxxxxx, platform-update-dev@xxxxxxxxxxx |
| cc: |
| Subject: [jdt-core-dev] org.eclipse.jdt.launcing.macosx & the Mac build |
>--------------------------------------------------------------------------------------------------------------------|
Hi folks,
So as part of the Mac build process we have grown a 2nd
org.eclipse.jdt.launching.* plugin. When we just had the J9 launching
plugin for Photon we just made the user eat the pain and download the
launcher separately. I know that the folks at QNX doing Photon development
would love a better out of box experience.
Talking to a couple of people there seem to be a few ways to do this.
1) Fold the two launcers (j9 and macosx) into org.eclipse.jdt.launching.
This is assuming they are small, can coexist on all platforms with no ill
effects and have no UI pressence.
2) Fess up to the fact that JDT has some platform dependant code and
morph/grow these launchers into fragments just like SWT does for their
platform code.
I will help, where I can, make either of these things happen but I need the
interested stake holders to decide on the best course of action.
...Dean...
