Description: Kconfigure simplifies compiling and installing software by providing a graphical interface.
Easy to use, just click the configure file in Konqueror and then configure, make and install the sources within kconfigure easy to use GUI. You can also pass configure and build arguments, log your install progress, and even use checkinstall to build (and install) rpm/slack/deb packages.Last changelog:
*Update: Added a src.rpm package. Please let me know if you create a package for a given distribution.
Version 2.1 includes Added: - Custom checkinstall options. - Qmake support. - Switched to a build install selector (instead of multiple install buttons.) - bzip files are now supported.
Fixed: - A bug that kept checkinstall and make install from working on Suse Linux. - A bug in the configure help system that kept any help info from loading into the dialog, thus making Configure Help worthless. - Dozens of other minor bugs.
Hello !
- When I click on the "install" button, I have a kdesu window to write the root password (Mandriva 2009.1 Spring) : normal.
But I haven't this window in Fedora/LXDE. Kdesu is installed but when I click on the "install" button, Kconfigure doesn't ask me the root password so it hasn't root privileges to proceed the installation.
- When I want to uninstall, I have the same thing even with Mandriva 2009.1 Spring version. Kconfigure doesn't uninstall because of non root rights.
Any idea to help me, please ?
Thank you in advance for your answer !
I would like to use this app. But I got a compile error like this: konq_actions.h:26:19: Fehler: qlist.h: Datei oder Verzeichnis nicht gefunde What is wrong? Thanks
I happened to have my favorite install on KDE in an alternative location. As such, I need to set the '--prefix=...' option with many configure runs. KConfigure (AWESOME program, by the way!!!) let's me "Configure with Arguments..." and provides a blank input box for me to type in any options. Well, I got tired enough of typing '--path=$KDEDIR' time after time, so I modified the source code to pre-fill the text box for me, so all I have to do is type in any thing else and hit enter.
Change line 454 of kconfigure.cpp:
KLineEditDlg argdlg( i18n("Configure with Arguments"), "--prefix=$KDEDIR", this);
I have just a little problem with my generated debs: they run on my system(because they compliled) but on another system they may not because the generated .deb does not have the dependency list. Their is an option to find find the dependecies? or i should look for them,but i don't know how?
I have found a script to dysplay all dependecies of program from source code:
#----------------------
strace -f -o /tmp/log ./configure
# or make instead of ./configure, if the package doesn't use autoconf
for x in `dpkg -S $(grep open /tmp/log|\
perl -pe 's!.* open\(\"([^\"]*).*!$1!' |\
grep "^/"| sort | uniq|\
grep -v "^\(/tmp\|/dev\|/proc\)" ) 2>/dev/null|\
cut -f1 -d":"| sort | uniq`; \
do \
echo -n "$x (>=" `dpkg -s $x|grep ^Version|cut -f2 -d":"` "), "; \
done
#----------------------
Maybe include it to put the corect dependencies of a .deb package :)
Hi! Nice work here...
I have some suggestions:
1. Could you please add support to make the last part of the proses (checkinstall etc.) as root even if the program is run as user? A pop up window asking for root password, like kdesu, is a nice solution because I want to run as root the least I can.
2. As for the checkinstall there should be some way of configuring some aspects like the package version number. I have seen that when run from a terminal it asks for these info.
3. A customizable location to store the generated deb's, rpm's etc. when they are made.
4. And at last but not least: add a wizard mode! Then your program is going to be veeeeeery great and could become a core KDE utility (even including it with the official release).
Thank you very much for Kconfigure I really like it.
Glad you like the program:
1. If "Check Install" or "Make Install" is selected as the install type (you can find the option in the Build menu) it should pop-up a root password request when installing. If it is not doing this for you please let me know.
2. There is. In the configuration dialog choose Check Install. There is a text area (version 2.1) titled Custom Options. There you can pass checkinstall whatever install options you like. Check out the checkinstall man-page for information on available options. But there definitely needs to be a per-build option for this (as opposed to a system wide configuration)... something along the lines of the "Configure Help" tool. Thanks for the idea, I will add it to the TODO.
3. All generated RPM files are "dumped" into your systems RPM build directory. This is set by RPM itself and not by either checkinstall or Kconfigure. You can change the default install location (for the root user, who is the user building packages for checkinstall) by creating a file in your roots home directory called .rpmmacros and adding this line to it:
%_rpmdir /location/where/I/want/my/rpms
Hope that helps.
4. Its like you read my mind! Check out the TODO file in Kconfigure's source. It lists the planned features for Kconfigure. A setup wizard and an application wizard are DEFINITELY planned, but I have to get a little more infrastructure work first.
Thanks for the feedback... home this helps with some of your concerns.
Bobby
In order to get the rpm to build I had to make a small adjustment
cd /directory/with/tarball
tar -vzxf kconfigure-2.1.tar.gz
mv kconfigure kconfigure-2.1
tar -czf kconfigure-2.1.tar.gz kconfigure-2.1
Then rpm builds fine.
you could still have created the rpms using:
BuildRoot: %{_tmppath}/%{name}
%setup -q -n %{name}
(provided that you had already defined %{name} on the "Name:" tag )
actually, if pass -n to %setup, the folder's name could be completly different from "Name:"
Opps... I should have set the %setup -n option in the spec file. It will be updated in CVS so this should not be a problem in future version of Kconfigure. Thanks for the heads-up.
Bobby
i havent seen the third screen shot... now i know about this program checkinstall so I will get the sources of ya program checkinstall them,now i have the debian package and i install this program
Here the output of make:
make all-recursive
make[1]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure'
Making all in doc
make[2]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc'
Making all in en
make[3]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc/en'
/usr/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
make[3]: Leaving directory `/home/frost/downloads/programme/tarballs/kconfigure/doc/en'
make[3]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc'
make[3]: F
Andreas can you email me directly? You can find my email address in the AUTHORS file (within the kconfigure source package.) Second author on the list. We will get you working!
Bobby
Why not add some specific distro flags in the configuration.
example: checkinstall flags for Mandrake would be: --pkgarch=i586 --pkgrelease=1mdk
Increasing pkgrelease at each build would be cool too.
Having the hability to join post/pre:un/install script would be cool.
An excellent thing would also to be able to chose the group.
example: in Mandrake http://www.linux-mandrake.com/en/howtos/mdk-rpm/mdk-rpm.html#MDK-GROUPS
groups are not the same as RedHat. Having a dropdown menu would help to chose correct values.
Having the ability to check for dependancies would be great too (looking at "checking for" lines during configure phase, search fo the stuff, locate package containing it and create the Requires: line) (very HARD imho but feasable).
An other option would be to propose Require fields.
Or better: juste befor install, open a fill'in form with missing fields like packager, URL, Requires, ....
that would be just like a print dialog.
=> Doing a dialog box analog to a print dialog with fields to fill in before realy create the package would be awesome :-)
Finaly the ability to also generate the SRPM would greatly help as it would allow to tweak it :-)
Anyway, V2.0 is already awesome :-)
Has anyone found a packaged RPM for KConfigure 2.0 for the following distributions: SuSE Linux or Red Hat Linux?
Will the developer be providing packaged RPM for KConfigure?
to create packages for any distro:
tar xvfj kconfigure-2.0.tar.bz2
cd kconfigure-2.0
./configure --prefix=/usr
make
make install
kconfigure
enable checkinstall
(example for Mandrake:
/usr/bin/checkinstall --pkgarch=i586 --pkgrelease=1mdk)
select configure script
configure
make
install as root
install package. It will overwrite the files installed in /usr by make install and then you'll be able to depollute you system in case you want to remove kconfigure.
I think I nice added feature would be to include checkinstall (http://checkinstall.izto.org/) with this. Not that I'm lazy .. got no problems compiling from the console .. it's just nice to see a gui do it! Dag, to bad I don't program!
Hopefully .. this can be done! =)
Thanks!
I should have bounced over to the homepage for this project first. There it is right on the homepage! Grrrrr! Of anything this is a good thing! Thanks for having that good idea before I even thought about it.
Hi!
Where would I find the settings option to set build arguments? In this new version this is nowhere to be found, so only plain i386 can be build...
J.
Ratings & Comments
37 Comments
Hello ! - When I click on the "install" button, I have a kdesu window to write the root password (Mandriva 2009.1 Spring) : normal. But I haven't this window in Fedora/LXDE. Kdesu is installed but when I click on the "install" button, Kconfigure doesn't ask me the root password so it hasn't root privileges to proceed the installation. - When I want to uninstall, I have the same thing even with Mandriva 2009.1 Spring version. Kconfigure doesn't uninstall because of non root rights. Any idea to help me, please ? Thank you in advance for your answer !
I would like to use this app. But I got a compile error like this:
konq_actions.h:26:19: Fehler: qlist.h: Datei oder Verzeichnis nicht gefunde
What is wrong? Thanks
Sorry. I'm using kubuntu 5.10 with KDE 3.4.3
Try to install devel/libqt3-compat-headers
I happened to have my favorite install on KDE in an alternative location. As such, I need to set the '--prefix=...' option with many configure runs. KConfigure (AWESOME program, by the way!!!) let's me "Configure with Arguments..." and provides a blank input box for me to type in any options. Well, I got tired enough of typing '--path=$KDEDIR' time after time, so I modified the source code to pre-fill the text box for me, so all I have to do is type in any thing else and hit enter. Change line 454 of kconfigure.cpp: KLineEditDlg argdlg( i18n("Configure with Arguments"), "--prefix=$KDEDIR", this);
Debian Unstable avaiable at: http://download.codigolivre.org.br/pacotesdeb/kconfigure_2.1-1_i386.deb
I have just a little problem with my generated debs: they run on my system(because they compliled) but on another system they may not because the generated .deb does not have the dependency list. Their is an option to find find the dependecies? or i should look for them,but i don't know how?
I have found a script to dysplay all dependecies of program from source code: #---------------------- strace -f -o /tmp/log ./configure # or make instead of ./configure, if the package doesn't use autoconf for x in `dpkg -S $(grep open /tmp/log|\ perl -pe 's!.* open\(\"([^\"]*).*!$1!' |\ grep "^/"| sort | uniq|\ grep -v "^\(/tmp\|/dev\|/proc\)" ) 2>/dev/null|\ cut -f1 -d":"| sort | uniq`; \ do \ echo -n "$x (>=" `dpkg -s $x|grep ^Version|cut -f2 -d":"` "), "; \ done #---------------------- Maybe include it to put the corect dependencies of a .deb package :)
Hi! Nice work here... I have some suggestions: 1. Could you please add support to make the last part of the proses (checkinstall etc.) as root even if the program is run as user? A pop up window asking for root password, like kdesu, is a nice solution because I want to run as root the least I can. 2. As for the checkinstall there should be some way of configuring some aspects like the package version number. I have seen that when run from a terminal it asks for these info. 3. A customizable location to store the generated deb's, rpm's etc. when they are made. 4. And at last but not least: add a wizard mode! Then your program is going to be veeeeeery great and could become a core KDE utility (even including it with the official release). Thank you very much for Kconfigure I really like it.
Glad you like the program: 1. If "Check Install" or "Make Install" is selected as the install type (you can find the option in the Build menu) it should pop-up a root password request when installing. If it is not doing this for you please let me know. 2. There is. In the configuration dialog choose Check Install. There is a text area (version 2.1) titled Custom Options. There you can pass checkinstall whatever install options you like. Check out the checkinstall man-page for information on available options. But there definitely needs to be a per-build option for this (as opposed to a system wide configuration)... something along the lines of the "Configure Help" tool. Thanks for the idea, I will add it to the TODO. 3. All generated RPM files are "dumped" into your systems RPM build directory. This is set by RPM itself and not by either checkinstall or Kconfigure. You can change the default install location (for the root user, who is the user building packages for checkinstall) by creating a file in your roots home directory called .rpmmacros and adding this line to it: %_rpmdir /location/where/I/want/my/rpms Hope that helps. 4. Its like you read my mind! Check out the TODO file in Kconfigure's source. It lists the planned features for Kconfigure. A setup wizard and an application wizard are DEFINITELY planned, but I have to get a little more infrastructure work first. Thanks for the feedback... home this helps with some of your concerns. Bobby
In order to get the rpm to build I had to make a small adjustment cd /directory/with/tarball tar -vzxf kconfigure-2.1.tar.gz mv kconfigure kconfigure-2.1 tar -czf kconfigure-2.1.tar.gz kconfigure-2.1 Then rpm builds fine.
you could still have created the rpms using: BuildRoot: %{_tmppath}/%{name} %setup -q -n %{name} (provided that you had already defined %{name} on the "Name:" tag ) actually, if pass -n to %setup, the folder's name could be completly different from "Name:"
Opps... I should have set the %setup -n option in the spec file. It will be updated in CVS so this should not be a problem in future version of Kconfigure. Thanks for the heads-up. Bobby
Can this program used for making packages(debs,rpm,mdk.rpm,tgz..) this would be cool having the source code and a program for making make the package
i havent seen the third screen shot... now i know about this program checkinstall so I will get the sources of ya program checkinstall them,now i have the debian package and i install this program
Here the output of make: make all-recursive make[1]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure' Making all in doc make[2]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc' Making all in en make[3]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc/en' /usr/bin/meinproc --check --cache index.cache.bz2 ./index.docbook make[3]: Leaving directory `/home/frost/downloads/programme/tarballs/kconfigure/doc/en' make[3]: Entering directory `/home/frost/downloads/programme/tarballs/kconfigure/doc' make[3]: F
Andreas can you email me directly? You can find my email address in the AUTHORS file (within the kconfigure source package.) Second author on the list. We will get you working! Bobby
Why not add some specific distro flags in the configuration. example: checkinstall flags for Mandrake would be: --pkgarch=i586 --pkgrelease=1mdk Increasing pkgrelease at each build would be cool too. Having the hability to join post/pre:un/install script would be cool. An excellent thing would also to be able to chose the group. example: in Mandrake http://www.linux-mandrake.com/en/howtos/mdk-rpm/mdk-rpm.html#MDK-GROUPS groups are not the same as RedHat. Having a dropdown menu would help to chose correct values. Having the ability to check for dependancies would be great too (looking at "checking for" lines during configure phase, search fo the stuff, locate package containing it and create the Requires: line) (very HARD imho but feasable). An other option would be to propose Require fields. Or better: juste befor install, open a fill'in form with missing fields like packager, URL, Requires, .... that would be just like a print dialog. => Doing a dialog box analog to a print dialog with fields to fill in before realy create the package would be awesome :-) Finaly the ability to also generate the SRPM would greatly help as it would allow to tweak it :-) Anyway, V2.0 is already awesome :-)
Has anyone found a packaged RPM for KConfigure 2.0 for the following distributions: SuSE Linux or Red Hat Linux? Will the developer be providing packaged RPM for KConfigure?
Packaged SuSE Linux RPM at http://linux01.gwdg.de/%7Epbleser/ Cheers :)
to create packages for any distro: tar xvfj kconfigure-2.0.tar.bz2 cd kconfigure-2.0 ./configure --prefix=/usr make make install kconfigure enable checkinstall (example for Mandrake: /usr/bin/checkinstall --pkgarch=i586 --pkgrelease=1mdk) select configure script configure make install as root install package. It will overwrite the files installed in /usr by make install and then you'll be able to depollute you system in case you want to remove kconfigure.
I think I nice added feature would be to include checkinstall (http://checkinstall.izto.org/) with this. Not that I'm lazy .. got no problems compiling from the console .. it's just nice to see a gui do it! Dag, to bad I don't program! Hopefully .. this can be done! =) Thanks!
I should have bounced over to the homepage for this project first. There it is right on the homepage! Grrrrr! Of anything this is a good thing! Thanks for having that good idea before I even thought about it.
Hi! Where would I find the settings option to set build arguments? In this new version this is nowhere to be found, so only plain i386 can be build... J.
In the "build" menu you can find option boxes to pass configure and make arguments. Here is a screenshot of the menu: http://kconfigure.sourceforge.net/images-2.0/kconfigure_dialog4.png Bobby