This is a discussion on Re: KDevelop project not ready for KDE SVN integration - KDE ; --===============1653393652== Content-Type: multipart/signed; boundary="nextPart1251147.oOI3J9jEWt"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1251147.oOI3J9jEWt Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 10 July 2005 03:45 pm, Nicolas Ternisien wrote: > Hi folks! > > I would like to know why KDevelop template are ...
--===============1653393652==
Content-Type: multipart/signed;
boundary="nextPart1251147.oOI3J9jEWt";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart1251147.oOI3J9jEWt
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sunday 10 July 2005 03:45 pm, Nicolas Ternisien wrote:
> Hi folks!
>
> I would like to know why KDevelop template are not ready for integration
> with KDE SVN. I'm the developer of KSystemLog project, available in
> playground/sysadmin tree of KDE repository, and my project had been fixed
> to allow it being compiled from KDE SVN tree. I know that this is not very
> well to commit something that don't compile on KDE repository, but I didn=
't
> know that.
>
> My problem is that now, I am unable to compile my local copy of KSystemlog
> with KDevelop.
>
> I know that the problem is that between my copy and the SVN one, the main
> different is that the compilation folder is playground/sysadmin, and in my
> project it is ksystemlog itself, but I'm not very kind of autotools (and
> more even now that I know KDE will soon change its build tool.)
>
>
> So, I would like to know, why, when we love GUI, we have to use shell to
> compile our projects, and why it is so difficult to use KDevelop projects
> when our sources are integrated in KDE repository tree.
>
> In fact, KDevelop and KDE SVN repository are not really integrated (or
> anyway it's difficult IMO to use them)
>
> I would like to have your feedback about my issue and if you have any
> solution/improvement to solve this one.
>
> Thanks !!!!
>
>
> Nicolas.
depending on the layout of your local checkout, you make have to config=20
kdevelop to look in certain spots for the builddir and the top_srcdir.
I'd need to know more about how your checkout is set up in order to help yo=
u.
=2D-=20
Matt
--nextPart1251147.oOI3J9jEWt
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBC0bGDA6Vv5rghv0cRAr26AJwNG0OAHTLeE1UH9EJiu6 YIvplC1QCfeBgw
dm0VDA7WRfIlSgaMNjj7gK4=
=DEh5
-----END PGP SIGNATURE-----
--nextPart1251147.oOI3J9jEWt--
--===============1653393652==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
=
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=
e <<
--===============1653393652==--