
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
A tool to create KDE from scratch with a graphical UI. KDE packages can be updated via CVS, one or more packages can be selected for update/configure/build/install.
16 years ago
V 0.6.1
* Added telnet interface to see at work what you compilation at home is doing
V 0.6
* Redesigned GUI
(All icons taken from the kde artwork package)
* Default sounds from KDE (in /opt/kde3)
* Splash screen
* Chose player for sounds
* Additional sound for errors
* Change colors of output
V 0.5.1:
* added some tooltips in mainview
* added Flag to ignore compile errors to get the whole stuff compiled
* Filename of .cvspass was wrong
* Support for environment
* Selection of qt directory (untested)
* Added russian language (empty)
* run make install/uninstall as non-root. Maybe later change this by option
* Fixed doubling of packages when no config exists
* Packages now autodeleted list, was probably a memory leak
V 0.5:
* Checked tab order in every widget
* added support for debug
* added support for selecting destination path
* added i18n support for local language
* added german translation file
* added selectable wavs to play when finished and stopped
(if someone could tell me how to hear something...?)
* Once again added some packages
* All known packages are automatically added when not existing yet
* Storing dates works now (really!)
* make uninstall in context menu (not tested)
Solutions:
- as kdesu not works, make install is called as non-root. Best install kde to $HOME/kde
- cvs login "works" if you call qbuildkde in console. When asked for password just press enter. Sorry, did not get it better. But dont mind, its only if you never were logged in before.
- Added configuring of sound player
16 years ago
V 0.6.1
* Added telnet interface to see at work what you compilation at home is doing
V 0.6
* Redesigned GUI
(All icons taken from the kde artwork package)
* Default sounds from KDE (in /opt/kde3)
* Splash screen
* Chose player for sounds
* Additional sound for errors
* Change colors of output
V 0.5.1:
* added some tooltips in mainview
* added Flag to ignore compile errors to get the whole stuff compiled
* Filename of .cvspass was wrong
* Support for environment
* Selection of qt directory (untested)
* Added russian language (empty)
* run make install/uninstall as non-root. Maybe later change this by option
* Fixed doubling of packages when no config exists
* Packages now autodeleted list, was probably a memory leak
V 0.5:
* Checked tab order in every widget
* added support for debug
* added support for selecting destination path
* added i18n support for local language
* added german translation file
* added selectable wavs to play when finished and stopped
(if someone could tell me how to hear something...?)
* Once again added some packages
* All known packages are automatically added when not existing yet
* Storing dates works now (really!)
* make uninstall in context menu (not tested)
Solutions:
- as kdesu not works, make install is called as non-root. Best install kde to $HOME/kde
- cvs login "works" if you call qbuildkde in console. When asked for password just press enter. Sorry, did not get it better. But dont mind, its only if you never were logged in before.
- Added configuring of sound player
slesa
16 years ago
Report
eriksjolund
16 years ago
http://www.abc.se/~m10828/adivobuilder/html/screenshots.html
I wrote it two years ago. It was a great way to learn kde programming. I don't think it has been used much. Not even by me. Feel free to take code or ideas from it ...
Report
slesa
16 years ago
Right now I am in a bit trouble (at the office), so I do not have the time to look carefully at it.
Any great things I can look for? One problem is, that it depends a lot on kde itself, so I have to retranslate it back to qt.
Report
eriksjolund
16 years ago
compiles on Fedora Core 2 ( kdelibs-3.2.2, gcc-3.3.3 ).
http://www.abc.se/~m10828/adivobuilder/src/
Here are some features:
building and install commands are written in a table ( where cvs modules are
on the y-axis ).
a similar table exists for specifying the working directories for the
commands.
updates from cvs ( also with cvsup or rsync )
collects the available cvs tags from viewcvs, ( for instance from
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/ )
configuration is saved in a xml file
Start adivobuilder and open the file examples/kdecvs.adivobuilder to see how it works.
cheers, Erik Sjölund
Report
slesa
16 years ago
But I'd like to support the cvs tags and cvsup/rsync, too. The only thing is: it must not depend on kde itself...
Report
eriksjolund
16 years ago
http://www.abc.se/~m10828/adivobuilder/html/kdecvs/
I used an XSLT script for this ( xslt/adivobuilder.xsl ).
Right now I have some other projects to take care of, so I don't think I will have time to code any new stuff for qbuildkde or adivobuilder. But I will try to answer your questions...
I am bit curios: Why do you want to do a pure QT-app?
Report
slesa
16 years ago
The idea behind is: download qbuildkde, press the button, wait what happens - in best case kde is ready then.
Only one problem is left: how to avoid depency failures within the packages (xxx-devel is missing)...
Report
eriksjolund
16 years ago
A Qt app is possible to build statically. That is no shared libraries, and hence no dependency on the Qt-library. But I guess building statically is not possible for a KDE app.
A user without any QT- and KDE-libs could just download your statically built Qt app and start from there.
This make sense. But in my opinion the common situation would be that QT and KDE already are installed.
Maybe a Qt app is a better way to go. I don't know...
Report
Diablo82
16 years ago
Report
pynm0001
16 years ago
The nice thing about this program is that it is GUI driven, making it even easier for people to install a CVS version of KDE. Beyond that I'm not sure, as I've never used it myself.
Report
slesa
16 years ago
Another task would be to compile kde on win32. Anyone tried it?
Report
Diablo82
16 years ago
Report
slesa
16 years ago
If this is easier now, I can have a look at it. If someone has expirieces that way - feel invited.
Report
virgiln
16 years ago
Thanks,
Virgil
Report
slesa
16 years ago
Report
pynm0001
16 years ago
$ tar xzvf archive-version.tar.gz
the files are extracted in the *current* directory instead of being extracted into the directory archive-version.
When you package your program, you should create a temporary directory, copy the files that will be in the package into this temporary directory, and then tar up the directory, not the files.
Example:
$ mkdir qbuildkde-0.6
$ cp source.* qbuildkde-0.6
$ tar czf qbuildkde-0.6.tar.gz qbuildkde-0.6
$ rm -r qbuildkde-0.6
Your archive is now contained within qbuildkde-0.6.tar.gz, and will not spill files all over a user's home directory when he extracts it. ;-)
Report
slesa
16 years ago
Sorry about that
Report
slesa
16 years ago
Report
pynm0001
16 years ago
Report
yf12s
16 years ago
Report
slesa
16 years ago
And what about the depencies (kdeextragear-lib1 for example)?
Maybe this can be solved by qbuildkde, but then make uninstall must be implemented from each package.
Report
anderslund
16 years ago
Report
slesa
16 years ago
Report
yf12s
16 years ago
Report
slesa
16 years ago
Report