Unstable development, guile 1.8 and gcc 4.5.2

Geert Janssens janssens-geert at telenet.be
Tue Mar 22 11:02:45 EDT 2011


On dinsdag 22 maart 2011, Derek Atkins wrote:
> Geert Janssens <janssens-geert at telenet.be> writes:
> 
> [snip]
> 
> > What do you think ? Which solution would be preferable and realistic
> > (in terms of effort vs gain) ?
> 
> I think it would be cool if there were some way in the 'branch' to say
> what build system is required.  Then we could effectively do:
> 
> - checkout branch/tag
> - run "the buildsys requires script from the checkout"
> - build the checkout
> 
> Perhaps we would need to have a local mapping of buildsys names to local
> paths, but this would make it future-proof.  If we require additional
> build environments we just install them side-by-side, create a global
> name and extend the local map, and then we just declare which buildsys
> we need to use.
> 
> > Geert
> > 
> > [1] https://bugzilla.gnome.org/show_bug.cgi?id=621238
> > [2] https://bugzilla.gnome.org/show_bug.cgi?id=615168
> 
> Keep in mind that tag build always rebuild all dependencies from
> scratch, so this approach would work.
> 
> Similarly, if we were going to set up a daily or weekly "branch build"
> then we would need a separate checkout and could certainly have a
> separate set of dependencies there, too.
> 
> -derek
I have been looking a bit closer at the msys/mingw interaction, to see if we 
could pull off having one msys installed but use different mingw environments 
based on what is required for the current build.

It looks like this can be implemented relatively easily. The key is that the 
only thing linking one mingw installation with msys is a line in Msys' 
/etc/fstab. This can be changed arbitrarily to swap mingw environments it 
seems. The change is visible immediatly, so you can do this even in a script.

The only caveat I see is that since there's only one msys and hence only one 
fstab file, you can't run two builds requiring different msys environments at 
the same time.

I will try to work out a few updates to the build scripts to get this going 
and report back.

Geert


More information about the gnucash-devel mailing list