[GEM-dev] MinGW build progress

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-08-24 19:27, Hans-Christoph Steiner wrote:
> An essential part of the whole Pd-extended build process is making sure
> that all the pieces are there. 

sure.

> Using make -k prevents that from
> working.

i don't see how.

using "make -k", the build will _still fail_ if one of the sub-targets fail.
the main difference is, that before failing, it will eat a lot more
ressources, as it goes on compiling the rest of Pd-extended.

personally, i "quite often" (at least that is my feeling :-)) look at
the build logs to see whether anything went wrong in parts that lie
within my responsibility.
if so, i try to fix these things asap.

imagine trivial bugs in "Gem", "iemnet", "iemguts" and "zexy" that
produce an FTBFS on various non-linux platforms for all those.
even if manage to fix the Gem part after the 1st build, it will take at
least 3 more nights to get noticed of the other problems.

if the builds are not for devs to fix their FTBFS bugs, then we could
probably turn off the automatic mailing of the build-logs to pd-cvs at .


fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5WCAoACgkQkX2Xpv6ydvTImACgq5ZGY9UidjWobY0Wh8n8rX0i
ZBYAoMlCQ/6nwu8dx41NqfWxuq1Nix0x
=g7qF
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20110825/b19d52c6/attachment.bin>