Community
Participate
Working Groups
Build Identifier: Eclipse IDE for Parallel Application Developers - Version: Indigo Service Release 1 - Build id: 20110916-0149 I use PTP (Eclipse IDE for Parallel Application Developers - Version: Indigo Service Release 1 - Build id: 20110916-0149). My OS is Ubuntu 11.10. In my workspace, I have a c++ and a fortran projects : 1. these projects are NOT MPI projects : run and debug are related to a "c++/fortran local application" configuration 2. these projects are stand-alone : not depending on any other project 3. both projects run OK : when I run c++ ( resp. fortran ) projet, only the build of c++ ( resp. fortran ) projet is triggered and then project is ran OK. Then I create a third project : this is a stand-alone MPI project (not depending on any other project). With the MPI project, run and debug are related to a "parallel application" configuration. Run and debug are OK but running MPI project triggers always a "build all" (that is building c++ project, then building fortran project, then building and running MPI project). Note: same behavior if the MPI project is a "Makefile project" or a "Wizard Hello World MPI project" When c++/fortran are "light" (hello world project), this problem is just annoying but not cumbersome... But when c++/fortran are "heavy" (lot of source to compile), this problem may become cumbersome ! Note: by pass found here http://wiki.eclipse.org/PTP/FAQ#Q:_When_I_launch_a_parallel_job_how_do_I_stop_it_from_building_everything_in_my_workspace_.3F FH Reproducible: Always Steps to Reproduce: 1. in a workspace, create non MPI projects and configurations 2. in the same workspace, create a MPI project 3. run MPI project with a "parallel application" configuration => triggers "build all" instead of "build"
This bug is closely related to bug 357994.
I'm not sure exactly what is being asked for here. The 'Build before launching' option is something that the platform provides and I'm not sure that we have any control over. Is disabling this option not sufficient, or is there something else you would like?
I think the confusion is that launching a parallel app rebuilds everything, but launching a non-parallel app only rebuilds itself
I confirm what Beth said in comment 3 : the problem I underlined is that launching a parallel application rebuilds everything (this may take a long time to re-build projects that are not related to the one that is supposed to be built). This "bug" is actually a kind of suggestion : if it can be changed (= launching a parallel application rebuilds only itself and his dependencies) I believe it could be a good thing. If it can not be changed, I will live with it as there is a by-pass FH
The 'Build before launching' option seems to be turned off by default for the Juno version of Eclipse for Parallel Application Developers. Other Juno packages have this option on by default. Was this done intentionally? I could not find the change in the repository. Unfortunately, turning this off by default affects other project types, which now no longer build before launching.
Yes it has been turned off by default. The reasoning is that most developers using PTP would rather have it off (based on the number of complaints we see) since it is annoying for C/C++/Fortran, and becomes even more of an issue for remote builds. It's really something that only Java developers want.
It is annoying in PTP because the auto-build in the PTP launch dialog is completely broken. Since it might build the wrong configuration it doesn't fulfill the purpose to make sure the project is build before launching it. But I disagree that it isn't useful for local CDT projects. It works fine. And CDT (including the CDT EPP) has it enabled. I don't think it is good practice to change defaults settings which effect other plugins (in this case effecting local CDT projects). Instead we should remove auto-build support from the remote launch dialog until it is fixed.
Maybe CDT developers like it, but maybe they turn it off also. In any case, it's an issue that is commonly raised, to the extent that we show how to disable it as part of the tutorial because it causes so many problems. I don't see an issue with changing a default preference behavior to suit our community. Incidentally, this was supposed to be the default for 5.0 but the setting was wrong in the product file. I don't see how removing auto-build support from the launch configuration helps this issue. A better solution would be to fix the auto-build support if it is broken, then disable that setting by default.
