--===============0666887022==
Content-Type: multipart/signed;
boundary="nextPart16307705.fm2msGizc8";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart16307705.fm2msGizc8
Content-Type: multipart/alternative;
boundary="Boundary-00=_Kju3Ig9X1IX6mLh"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--Boundary-00=_Kju3Ig9X1IX6mLh
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
On Friday 26 September 2008, Robert Zwerus wrote:
> Hey people
>
> I'd like to use kdesvn-build and Eclipse together. Unfortunately, Eclipse
> makes working with out-of-source builds a bit harder than necessary, so I
> opt for in-source builds.
>
> I added support for it to the kdesvn-build script, a patch against the
> current SVN version is attached.
>
> When it's okay with you, I'd like to commit it.
Robert,
I see you emailed me about the patch, I apologize for not having time to lo=
ok=20
at it.
But first I'd like to ask you to test the following setting for the build-d=
ir=20
option:
build-dir ${source-dir}
This should set the build-dir to whatever the source-dir is for that module=
=20
(even if you only make this change in your global options). My testing see=
ms=20
to show that this will only work if you use a source-dir of ~/foo/bar or=20
/foo/bar (and not simply foo/bar).
I'd like to avoid patching if possible, especially if this solution works=20
(especially since I don't think it seems to much of a hack, situations like=
=20
this is why I added support for ${option-name} in the config file)
Regards,
- Michael Pyne
--Boundary-00=_Kju3Ig9X1IX6mLh
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: 7bit
On Friday 26 September 2008, Robert Zwerus wrote:
> Hey people
>
> I'd like to use kdesvn-build and Eclipse together. Unfortunately, Eclipse
> makes working with out-of-source builds a bit harder than necessary, so I
> opt for in-source builds.
>
> I added support for it to the kdesvn-build script, a patch against the
> current SVN version is attached.
>
> When it's okay with you, I'd like to commit it.
Robert,
I see you emailed me about the patch, I apologize for not having time to look at it.
But first I'd like to ask you to test the following setting for the build-dir option:
build-dir ${source-dir}
This should set the build-dir to whatever the source-dir is for that module (even if you only make this change in your global options). My testing seems to show that this will only work if you use a source-dir of ~/foo/bar or /foo/bar (and not simply foo/bar).
I'd like to avoid patching if possible, especially if this solution works (especially since I don't think it seems to much of a hack, situations like this is why I added support for ${option-name} in the config file)
Regards,
- Michael Pyne
--Boundary-00=_Kju3Ig9X1IX6mLh--
--nextPart16307705.fm2msGizc8
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEABECAAYFAkje6NIACgkQqjQYp5Omm0qUtACg2O2bQZVsL66r8eUBADvkXsf8
lvQAn2s+9JqYdjV8cLdB10qHkvWefc6k
=2pWI
-----END PGP SIGNATURE-----
--nextPart16307705.fm2msGizc8--
--===============0666887022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
--===============0666887022==--