В сообщении от Вторник 28 марта 2006 г. 05:05 Vadim Jukov написал(a): > Hello, dear all. > > I'm porting KDevelop now. It builds OKay, but when I try to make > simple (just created by wizard) project, it fails on automake. Yes, > I'm enough stupid to port KDevelop without knowing how does it works - > my programming expirence is limited almost to M$ and Web programming > (history of my switching to *nix world is something unrelated, I > think, so it's skipped here:)). So, please, hurt me with at least > telling direction.:) > > I made 2 ports some time ago but didn't send them to ports@ because I > don't think that ports for 2-year-still-unmaintained software are some > that OpenBSD is interested for. > > Port itself is attached also. I didn't tuned it up, because it'll need > tuning in any case, and I don't want to do the work 2 times:) (and > pathes directory is empty at this time - thanks for great ports > framework!). For example, by default KDevelop wants automake 1.6, > which is unsupported natively on OpenBSD. I just (re)defined following > make variables in sample project: > > WANT_AUTOCONF_VERSION_2_5 > -WANT_AUTOMAKE_VERSION_1_6 > +WANT_AUTOMAKE_VERSION_1_8 > +AUTOMAKE_VERSION=1.8 > +AUTOCONF_VERSION=2.57 > > I choosed 2.57 version for automake because output attached always > seem to use 2.57. But it doesn't matter, am I using > "AUTOCONF_VERSION=2.57" or "AUTOCONF_VERSION=2.59", even > "AUTOCONF_VERSION=2.13". > > Also I set up make program to "make". By default, KDevelop starts > "gmake" (attached log produced by "make"). But this doesn't make any > sense, only output format changes a bit; errors are the same. > > Every help willi be appreciated very much! > > At this time I has installed: > > 04:39 /usr/ports/devel/kdevelop$ pkg_info | grep auto > autoconf-2.13p0 automatically configure source code on many Un*x > platforms > autoconf-2.52p0 automatically configure source code on many Un*x > platforms > autoconf-2.54 automatically configure source code on many Un*x > platforms > autoconf-2.56 automatically configure source code on many Un*x > platforms > autoconf-2.57 automatically configure source code on many Un*x > platforms > autoconf-2.58 automatically configure source code on many Un*x > platforms > autoconf-2.59 automatically configure source code on many Un*x > platforms > automake-1.4.6 GNU Standards-compliant Makefile generator > automake-1.8.5 GNU standards-compliant Makefile generator > automake-1.9.6p0 GNU standards-compliant Makefile generator > metaauto-0.5 wrapper for gnu auto* > > All versions of automake were installed for this port purposes only.:)
With help of David Love new version of port became for review. Let's call
it RC1:). Now I say: "please test", because port actually works and
looks like a real port. :)
Attaching new version of a port. After some thinking I moved it from
${PORTSDIR}/devel/ to ${PORTSDIR}/x11/kde/ because even it's source
files share same dir with KDE ones. :) So untar port in
${PORTSDIR}/x11/kde. Oldd irectory can be removed, though.
I added a patch (first patch for such big project! Thank you, OpenBSD
team, especially Marc Espie, and, of course, KDE team that writes really
portable code!:)) that tweaks a file
(${WRKSRC}/languages/cpp/app_templates/kscons_kxt/app.kdevelop), which
is being used as source for many projects defaults. Please look at this
file, maybe you'll find something that has to be changed. At least, we
may force using native "make" instead of gmake. At this time that shows
up a bunch of problems: for example, cleaning project fails with "make"
but successfully ends up with "gmake".
Also there is archivied copy of this directory in itself, called
kscons_kxt.tar.gz, which, of course, also includes app.kdevelop. :-\ So
I tweaked Makefile, just see "post-patch" target.
BTW, some cleanup made (including DESCR - KDbg is something related of
course, but it is already there:)), and I marked self as maintainer (at
least I don't think about switching to anything else from KDE on
OpenBSD, so I will not forget to update port ;) ).
Now I'm having a small question about kdelibs documentation: is it
installed correctly and I heave to tweak KDevelop's configure (I tried
many values, nothing helps - it doesn't find documentation), or it's
just not maintained? And what are the plans for kde/kdoc3?
Now shutting down, going to work and waiting for your replies:).
--
Best wishes,
Vadim Jukov
develop3.tar.gz
Description: application/tgz
