After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 344888 - Add support to compile specific stages
Add support to compile specific stages
Status: RESOLVED OBSOLETE
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: James Henstridge
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2006-06-14 16:19 UTC by Jose Dapena Paz
Modified: 2008-06-22 19:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to add --stage parameter to build specific stages (5.07 KB, patch)
2006-06-14 16:25 UTC, Jose Dapena Paz
none Details | Review

Description Jose Dapena Paz 2006-06-14 16:19:46 UTC
In order to be able to integrate mozilla tinderbox with jhbuild, it's very interesting that we can run stages one by one. A solution is adding a parameter that specifies the compilation stage. In tinderbox the required stages are update, configure, build and install.
Comment 1 Jose Dapena Paz 2006-06-14 16:25:30 UTC
Created attachment 67346 [details] [review]
Patch to add --stage parameter to build specific stages

This patch adds a --stage parameter for "build" and "buildone" commands. It lets the user select the stage he wants to run from tinderbox (specifically update, configure, build and install).

If the stage is not supported by the module, it returns with success (needed for meta packages).
Comment 2 James Henstridge 2006-06-19 08:19:51 UTC
One issue with this is that not every module type will use the same set of stage names (e.g. the new "perl" module type has no configure stage).

Perhaps there is a different way of hooking jhbuild up to mozilla tinderbox in a way that provides a better fit?
Comment 3 Jose Dapena Paz 2006-07-04 15:09:32 UTC
Stages splitting give us more control over steps execution. Anyway, the only stage I would really require to be run separately is update, and currently there's already an option to do this.

Anyway my implementation offers a limited set of stages (update for checkout/download), configure (autogen+configure stuff), build (make/make all) and install. When you set a stage, it's run until next stage is another one of these 4, and if it's not available it runs silently without returning error (required to avoid problems running non existing steps).

Is there anyway to get a compromise over the name of 3 or 4 common stage names that could be used in a parameter like this one? I think these 4 cover nearly every project (without taking into account make-check's). Maybe I'm a bit biased by autotools projects. These stages would be optional (covering the perl case that do not provide "configure" or others not providing "build"). But a compromise on common names would avoid having configure-like tasks being named in different ways. It there's a compromise like this, this patch would be ok for the stage splitting goal.
Comment 4 Frederic Peters 2007-12-16 12:13:51 UTC
Jose, is this patch still necessary for the buildbot work ?  Otherwise I will mark this bug report as obsolete.
Comment 5 Frederic Peters 2008-06-22 19:57:08 UTC
Marking bug as obsolete; please feel free to reopen if needed.