[Digikam-devel] digikam project and kdevelop - questions

[Peter Heckert]

Hello,

here I am again. I was near to giving up, but finally I installed Fedora
core 5 instead of Kanotix/Debian
and now the debugger is working ok in kdevelop.

I can compile and debug the whole project, but I still cannot compile a
subproject e.g. noisereduction.
So compiling and installing is very timeconsuming.

I do this:
Open the automake manager. Goto noisereduction and click right mousebutton.
A contextmenu opens and gives several options. I choose "Build".
Then a Messagebox appears, saying:
"There is no Makefile in this directory. Run configure first?"

Ok, I know, there is a Makefile in this directory. When I invoke it from
console,
then the subproject alone is compiled and when I invoke "sudo make
install" then the plugin
alone is installed, and the full timeconsuming compilation- and
installation process is avoided.

However, when I do this from console then I dont get compiler messages
into kdevelops
message window and so I cannot jump into the editor, when there was an
compiling error.
What is missing here?

Another question: Debugging is ok, but the debugger is rather slow. I
believe, this is,
because the whole application is compiled with debugging option. The
symbol table is too large.
Is there a way to compile only the plugin with debug option?
Or, if not, can I strip debug symbols from the digikam executable, and
how can I do this?

I dont know if my version of kdevelop still has a problem. This is what
I have:

Qt: 3.3.5
KDE: 3.5.1-2.3 Red Hat
KDevelop: 3.3.1

TIA,

Peter

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

Le Vendredi 21 Avril 2006 11:55 PM, Peter Heckert a écrit :
> Hello,
>
> here I am again. I was near to giving up, but finally I installed Fedora
> core 5 instead of Kanotix/Debian
> and now the debugger is working ok in kdevelop.

Sounds good. It's better to use a pro linux dist when you is a linux beginner
(This is not a troll (:=)))). Personnaly i use Mandriva 2006 without problem.

>
> I can compile and debug the whole project, but I still cannot compile a
> subproject e.g. noisereduction.
> So compiling and installing is very timeconsuming.
>
> I do this:
> Open the automake manager. Goto noisereduction and click right mousebutton.
> A contextmenu opens and gives several options. I choose "Build".
> Then a Messagebox appears, saying:
> "There is no Makefile in this directory. Run configure first?"
>
> Ok, I know, there is a Makefile in this directory. When I invoke it from
> console,
> then the subproject alone is compiled and when I invoke "sudo make
> install" then the plugin
> alone is installed, and the full timeconsuming compilation- and
> installation process is avoided.
>
> However, when I do this from console then I dont get compiler messages
> into kdevelops
> message window and so I cannot jump into the editor, when there was an
> compiling error.
> What is missing here?

You cannot do that because Makefile are driven by automake/autoconf from main
root folder.

I you want only compiled NR folder, just remove all other plugins folder (like
adjustcurves, whitebalance, etc), excepted common folder.

After that, in Kdevelop just use digikamimageplugins.kdevelop project (n ot
digikam project), and restart Build/Run Automake & friends and Build/Run
Configure.

To optimize compilation time, you can remove doc folder and other extragear
apps source code.

>
> Another question: Debugging is ok, but the debugger is rather slow. I
> believe, this is,
> because the whole application is compiled with debugging option. The
> symbol table is too large.

compile digikam without debug options and install it.

> Is there a way to compile only the plugin with debug option?

Just use digikamimageplugins KDevelop project and recompile with full debug
options

> Or, if not, can I strip debug symbols from the digikam executable, and
> how can I do this?
>
> I dont know if my version of kdevelop still has a problem.

not Kdevelop. I recommend you to have a computer with a large RAM (500MB min.)

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Heckert]

Caulier Gilles wrote:
> Sounds good. It's better to use a pro linux dist when you is a linux beginner
> (This is not a troll (:=)))). Personnaly i use Mandriva 2006 without problem.
>  
I have been a linux beginner for several years ;-)
Was Mandrake (5.2-7.2) user for some years, then I switched to Fedora,
then to windows and now
back to Fedora ;-) I will never stop being a linux-beginner, because I
can never learn everything,
and I dont want to know everything, I have some ROI's (regions of
interest) and everything outside
should simply work automagically as advertised ;-)
>> I dont know if my version of kdevelop still has a problem.
 > not Kdevelop. I recommend you to have a computer with a large RAM
(500MB min.)
Have 1 GB and Athlon Duron 1,2GHz.

I  continue using the gimp-plugin for further development of dcamnoise.
It is better as a testbed, when I test out new features. Much faster
turnaround cycle and I can load
old and new plugin-versions at the same time and compare their image
quality onscreen.
So I will not show up here for some time.

I have started on a version that uses 2-dimensional edge detection. When
this is working I announce it,
then you can evaluate the gimp plugin. Should be easily portable,
because I use floating point,
16-bit is no problem and I use c++ now.

Intermediate development code and doc can always be found at the
gimp-registry.

Thank's for the help so far, it's much better using kdevelop than kwrite
and I hope this will speed
up my work.

best regards,

Peter
 
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel