[Kommander-devel] Re: kommander-devel

Eric Laffoon eric at kdewebdev.org
Sun Feb 10 01:20:09 EST 2008


On Saturday 09 February 2008 9:28:05 pm Dan Cherry wrote:
> On Friday 08 February 2008 8:03:36 pm you wrote:
> > On Friday 08 February 2008 11:55:19 am Dan Cherry wrote:
> > > ./admin/cvs.sh: 651: --version: not found
> > > *** AUTOCONF NOT FOUND!.
> > > *** KDE requires autoconf 2.53 or newer
> > > make[1]: *** [cvs] Error 1
> > > make: *** [all] Error 2
> > >
> > > (I have autoconf 2.61 installed, and accessible from a terminal, and
> > > cvs 1.12.13 also installed and accessible from a terminal)
> >
> > Any update?
>
> I've got partial success...

Maybe more if you got all the details. ;)

> I was able to get my desktop to compile kommander successfully, and the
> plug-ins indicated that they compiled, but kommander couldn't load any of
> the plugins.

How did you try? With the plugins you use either the included plugin loader or 
the Kommander editor and select the *.la file in the build directory. If you 
don't do that you don't have plugins. I guess we could also install them 
globally, but they're plugins.

> Less luck with my laptop.  I tried for several hours to get kommander to
> compile using the svn repositories.  Finally, I copied the kdewebdev
> directory from my desktop to the laptop, and it compiled with no problems.
> Any chance the svn was broken?

Not likely. Either your laptop has something different... or you copied your 
build information to another build. That's why I suggested
mkdir build
cd build
../configure
instead of
./configure
You can trash a build and delete it and start over without having to re-get 
SVN.

Make sure not to copy the build directory if you are going to another machine 
as it will have likely erroneous information for that machine.

> So I currently have kommander 1.3 on both machines, but with no plugins
> (which I can live with for now.)

They are nice, and some features of development tools will depend on them, but 
for most people it will depend if you have a specific need. I use them a lot!
>
> But that leads to two new questions.
> If I run $svn up   from the kdewebdev directory, do I need to run all of
> the processes to recompile?
>
> cd kdewebdev
> make -f Makefile.cvs
> mkdir build
> cd build/
> ../configure
> cd kommander
> make
> sudo make install
>
> Or is there a shortcut to get the updates compiled?

If nothing new is added you can just do a make and make install. It's unlikely 
a lot will be added... actually some tools will be added shortly, so I take 
that back. If you see a message about missing make targets start at the head 
of that list and you should be fine.

>
> Also, I poked around in the new parser, and discovered that the ability to
> set a key/value pair for an array is no longer there.  I checked the new
> docs, and setValue is no longer there.  Is the array being replaced with an
> indexed only array?

Bzzt! Incorrect, but I see where you would get that idea. There is no longer a 
need to do array_setValue(x,y) so why have it
a["key"] = "val"
that works fine, as does
array_fromString("a", "1\ta\n2\tb\n3\tc")
which is the same as
a[1] = "a"
a[2] = "b"
a[3] = "c"

Pleas see the parser docs at the link I gave you in a previous email (you need 
to add the host in that link) or go to kdewebdev/doc/kommander/ and run 
meinproc index.docbook
which, assuming you do have all those dev tools, will create local HTML docs, 
with some weird glitches because their really for the help system.

the indexed arrays are for getting around 
"1\t2\t3"
or
"a\nb\nc"
which will give you one key with array_fromString for the first and three keys 
with the second... which is pretty worthless. The indexed functions will give 
you indexed arrays from both. They were created to avoid long ugly strings of 
str_section(TreeWidget1.selection, "\t", 5) and so on...
>
> Tomorrow, I'll take another stab at re-compiling the plug-ins, and updating
> the svn directories.

Plugins don't compile? Did you copy the admin directory from kdewebdev to each 
plugin directory? SVN would let us put an admin directory in there as they 
don't maintain it.
>
> again, thanks for the pointers

sure

-- 
Eric Laffoon
Project Lead - kdewebdev module


More information about the Kommander-devel mailing list