Warning: session_start(): open(/tmp/sess_o895elsno2gijrenn4ti5d3ek4, O_RDWR) failed: No space left on device (28) in /www/H01/htdocs/lib/base/lib_base.php on line 280
Kompile openDesktop.org


	KDE-Apps.org Applications for the KDE-Desktop GTK-Apps.org Applications using the GTK Toolkit GnomeFiles.org Applications for GNOME MeeGo-Central.org Applications for MeeGo CLI-Apps.org Command Line Applications Qt-Apps.org Free Qt Applications Qt-Prop.org Proprietary Qt Applications Maemo-Apps.org Applications for the Maemo Plattform Java-Apps.org Free Java Applications eyeOS-Apps.org Free eyeOS Applications Wine-Apps.org Wine Applications Server-Apps.org Server Applications apps.ownCloud.com ownCloud Applications


	KDE-Look.org Artwork for the KDE-Desktop GNOME-Look.org Artwork for the GNOME-Desktop Xfce-Look.org Artwork for the Xfce-Desktop Box-Look.org Artwork for your Windowmanager E17-Stuff.org Artwork for Enlightenment Beryl-Themes.org Artwork for the Beryl Windowmanager Compiz-Themes.org Artwork for the Compiz Windowmanager EDE-Look.org Themes for your EDE Desktop


	Debian-Art.org Stuff for Debian Gentoo-Art.org Artwork for Gentoo Linux SUSE-Art.org Artwork for openSUSE Ubuntu-Art.org Artwork for Ubuntu Kubuntu-Art.org Artwork for Kubuntu LinuxMint-Art.org Artwork for Linux Mint Arch-Stuff.org Art And Stuff for Arch Linux Frugalware-Art.org Themes for Frugalware Fedora-Art.org Artwork for Fedora Linux Mandriva-Art.org Artwork for Mandriva Linux


	KDE-Files.org Files for KDE Applications OpenTemplate.org Documents for OpenOffice.org GIMPStuff.org Files for GIMP InkscapeStuff.org Files for Inkscape ScribusStuff.org Files for Scribus BlenderStuff.org Textures and Objects for Blender VLC-Addons.org Themes and Extensions for VLC


	KDE-Help.org Support for your KDE Desktop GNOME-Help.org Support for your GNOME Desktop Xfce-Help.org Support for your Xfce Desktop

openDesktop.org: Applications Artwork Linux Distributions Documents Linux42.org OpenSkillz.com

Kompile

0.3 beta 3

KDE System Tool

Score 81%

invernomuto
Home

Link: Link
Downloads: 24928

Submitted: Oct 14 2005
Updated: Jun 9 2007

Description:

Finally the site www.brainspace.it is online again with Kompile v0.3 Beta 3.
I'm sorry for the long offline period.

WARNING: Version 0.3 beta 3 of Kompile may be unstable and is relase for testing purpose. If you find a bug and you want report it write me an e-mail: tommaso.frazzetto@gmail.com

I'll be grateful to anyone who help me make Kompile better.
Thanks

What's Kompile
Kompile is a KDE interface for automatic execution of configurations, compilation and installation of source tarball.
when you compile and install Kompile sources (with normal steps "configure && make && make install") some new voices are added to
konqueror action menu for tar-based compressed archives (.tar, .tar.gz, .tar.bz, .tar.bz2).

What's new in v0.3
The major innovation of version 0.3 is profiles system. Now Kompile always use a profile to perform an installation/uninstallation.
You can define a custom profile for install an application or use default profile to do it. If you use default profile, Kompile will
create a package's profile based on options specified in your default profile.
Some profiles options are:
- Source tarball backup for uninstallation
- Packages informations (name, version, release, license, description)
- Temporary decompression folder options
- Source configuration options (prefix, enable/disable warnings, enable disable libs such as Qtopia, etc.)
- Compiler options (c/c++/fortran compilers flags, executables, prerocessor flags,linker flags, etc.)
- Simple user (= non root) installation options
- Use checkinstall instead make install (and specify checkinstall options)

More screenshots:
You can find more screenshots at:
http://www.brainspace.it/index.php?option=com_content&task=view&id=23&Itemid=23

Usage
There are 3 modes to use kompile:
1) Run Kompile form KDE System menu and use GUI to invoke Kompile functions. There are 3 major icons:
- Install options:
- Standard installation: use default profile to install new package
- Profiled installation: create a new profile from scratch to perform installation
- Uninstall options:
- Standard uninstallation: remove a package using default profile (may be useful if installed pkg has different prefix form default)
- Repair/Remove Installed Packages: give a list of installed packages to perform package's repair/remove
- Tools:
- Manage Profiles: Modify/delete existing profiles
- Kompile Setup: here you can specify you preference for some kompile functions and MODIFY YOUR DEFAULT PROFILE

2) Invoke Kompile from command line whit below options (form "kompile --help" command):
-i, --install Perform install operation
-u, --uninstall Perform uninstall operation
-t, --use-tarball Use specified tarball for requested operation [need -i or -u]
-p, --use-profile Use specified profile for operation [need -i or -u. Exclude "--use-tarball"]
-s, --search-profile Use with "--use-tarball ".Kompile searches a profile compatible with "". If doesn't find one compatible use default profile.

3) Select operations directly form konqueror kompile menu:
- Perform default package installation: use default profile to install new package. It's equal to "kompile --install --use-tarball "
- Search compatible profile for installation: Kompile searches a profile compatible with "" to perform installation. If doesn't find one compatible use default profile. It's equal to "kompile --install --search-profile --use-tarball "
- Perform default package uninstallation: remove a package using default profile (may be useful if installed pkg has different prefix form default). It's equal to "kompile --uninstall --use-tarball "
- Search compatible profile for uninstallation: Kompile searches a profile compatible with "" to perform installation. If doesn't find one compatible use default profile.It's equal to "kompile --uninstall --search-profile --use-tarball "

# LICENSE
This software is released under GPL (GNU General Public License). Anybody can change and redistribute code under GPL terms.
For more info about GPL see "COPYING" in source package root folder.
For more information about GNU & GPL visit GNU site at:

http://www.gnu.org

# MORE INFORMATIONS
Project Home Page (In Italian): http://www.brainspace.it/index.php?option=com_content&task=view&id=17&Itemid=12

Screenshots Gallery: http://www.brainspace.it/index.php?option=com_content&task=view&id=10&Itemid=7

Download Page (In Italian): http://www.brainspace.it/index.php?option=com_content&task=view&id=17&Itemid=12

# PARTICULAR THANKS TO
Many people have manifested interest in Kompile project and I can't thank all one by one but I'm grateful to anyone.
This people have spent time in Kompile realization with ideas and resources. Thank you.

v0.3
- Urs Wolfer
- Folivier_L
- Marco E.V.
- Roberto F.
- Alfredo B.
- Vincenzo C.
- Bogusz Linda
- Carlos Gonçalves

Changelog:

- CHANGES FROM Beta 2 to Beta 3:
[] Profiles managemnt dialog redesigned.
[] Performance improved.
[] Corrected some bugs in profle creation for default install operation.
[] Fixed sintax problems in checkinstall invocation.
[] Minor bugs fixing
[] Polish language translation (Thanks to Bogusz Linda)

- FEATURES (v0.3):
[] Add standalone GUI for tarball packages management (you can access it form "System" menu)
[] General Kompile options, as:
* Selection of KDE-Integration menu type (actions menu/kompile standalone menu)
* Play sounds when installation/uninstallation finish
* Set time of automatic close installation/uninstallation dialog when finish
* Enable/Disable automatic close of installation/uninstallation dialog when finish by default
* Setup of default profile for standard installation/uninstallation
[] Add installation/uninstallation profiles system. Profiles options are:
Package info (name, version, release, license, description)
* Save of package's sources tarball for repair/uninstallation
* Temporary tarball decompression options
* Configuration flags (prefix, mobile app libs, debug, profiling, etc.)
* Simple user installation/uninstallation options
* Use of checkinstall instead of (make install)
[] Search existing compatible profile before installation
[] Pause/Resume button in installation dialog
[] Show package's "README" button in installation dialog (if package's README file is available)
[] Show package's "INSTALL" button in installation dialog (if package's INSTALL file is available)
[] Show package's "ChangeLog" button in installation dialog (if package's ChangeLog file is available)
[] Statistics/informations for each task in installation/uninstallation dialog
[] Manage of installed application with Repair/Remove tools
[] Italian translation

- CHANGES/FIXES
[] Use KProcess instead of QProcess (more KDE-compilance)
[] Use KDialogBase instead of QDialog (more KDE-compilance)
[] Use KpushButton instead of QPushButton (more KDE-compilance)
[] Add full translation support
[*] Removed traybar icon

License: GPL

Source

(v0.2 - stable)

Mandriva

(Mandriva RPM v0.2)

Slackware

(Slackware Package v0.2)

Source

(v0.3 beta 3)

Send to a friend
Subscribe
Other Content from invernomuto
Report inappropriate content

goto page:

... 4 5 6 7 8 9 10 11 12

Tarball

by saejoh on: Jun 14 2007

Score 50%

saejoh

Hi,
I used this app in its beta2 version.
Unfortunately this link http://www.kde-apps.org/content/download.php?content=30223&id=4 lets us download a tar.gz-file, which is impossible to be extracted as expected with Ark for instance. The extraction process results in numerous errors: ...Couldn't open file. Permission denied. Then follows a general error: Extraction failed.
So my question is: where can we find a proper tar.gz for this wonderful beta3? (I went back to beta2)
Thanks in advance.

Reply to this

Re: Tarball

by invernomuto on: Jun 17 2007

Score 50%

invernomuto
Home

Hi,
probably there was been an error during tarball creation.
I've uploaded a new tarball which should work.

Reply to this

Very nice...

by Contrast on: Sep 23 2007

Score 50%

Contrast

Are there any plans to implement support for programs that use setup.py for their installation? (And if so, would it be possible to make it so said programs could be uninstalled by Kompile even if the setup.py file doesn't include a rule for uninstalling?) That's the only thing I find lacking. Otherwise, keep up the great work! :-)

Reply to this

Kompile's Future!?

by dispatched on: Jan 2 2008

Score 50%

dispatched

kconfigure, kinstall, kompare, klik etc...

There are simply too many DIFFERENT efforts going on trying to provide the same sort of
functionality or even the same sort of app (guess how many of such similar tools for other
window manager might exist)! And apparently some projects are not even aware of the other
ones!?

That's BAD: open source is all about collaboration and not about cooking your own soup.

It should be possible to accomplish much more by uniting the manpower from all related
projects, so that these projects can be -functionality-wise- merged into a new fork
of all of these tools, ensuring that there is no unnecessary competition in an area
that has been successfully addressed on other platforms for decades already.

Apart from that, I truly like kompare-from its maintenance, UI and feature-richness point
of view, kompare is for sure the most advanced and promising utility in its category and
that's GREAT!

However, there are clearly some issues that -for the sake of kompare and its likely future
within KDE- should preferably be addressed, many of which were previously mentioned, but
some weren't yet-I would like to provide a number of enhancements and suggestions related
to turning kompile into a "software build manager":

- in certain situations, configuring a project requires pre-configuration:

some tarballs provide autogen.sh files specifically for this purpose, but
even if these are missing in the tarball itself, the autotools build files
can usually be re-created using autoconf, automake & co
It should be considered to provide optional support for "pre-configuration"
for packages that seem to make use of GNU autotools.

- configurable build directory location

in some situations it may make sense to use non-temporary build locations, that
may optionally not be deleted after installation

- repeated/incremental builds:

some projects may need to be regularly rebuild, so their folder must not be deleted

- decouple the configuration & build steps:

configuration is a step different from building: it doesn't necessarily
require root priviledges, nor will everybody usually/immediatley want to
run the build directly after the tarball's configuration: Steps that aren't
intertwined by default, should be properly separated and being dealt with
as separate entities. Some good suggestions related to kdesudo were already
made, in fact kconfigure also handles all steps separately.

- provide means to individually customize crucial configuration/build standard parameters and environment variables:

most scripts and tools used in the average linux/kde [GNU/autotools-based] tarball
use a predefined set of tools which usually supports a number of standard parameters
and honors certain environment variables (CC, CXX, CFLAGS, CXXFLAGS, LD_FLAGS,
LD_LIBRARY_PATH etc): advanced users may want to be provided with an overview of such
customizable attributes to show their contents and optionally edit/modify them, possibly
even allowing such users to save these settings in some sort of configuration/build profile.
This could for example be used to provide standard build profiles for use of ccache or distcc while
building.

- provide means to customize non-standard parameters:

by running configure --help, the configure script's help can usually be obtained,
this could in turn be used to enable users to pass certain arguments to the script,
this could for example be based on coming up with a suggestion for the argument
name (retrieved from parsing the output), accompanied by a description/tooltip
coming from the description of the argument in the --help output, and then a
textbox/file picker dialog to optionally provide additional info, i.e. for cases
where additional information needs to be passed: ./configure --with-foo=path/to/foo

- interactive default mode while running kompile under KDE/X without arguments:

it might make sense to consider automatically going into interactive/GUI mode
when no parameter were provided, if the DISPLAY variable is set, you can assume
that X is available and anyone running kompile from a shell without arguments,
will probably want to start it in interactive mode, where the tarball can be chosen
from within the UI.

- build management/scheduler:

in some situations it may be desirable to postpone the compilation/build process of
a large -already configured- software project, thus it would be useful if there
was some sort of process (or even daemon) that could act as a build scheduler, which
would trigger builds based on certain criteria/conditions.
For example: I regularly rebuild large software packages such as kde, gcc and mozilla,
however I don't want this to interfere with my daily use of the machine, so I usually
postpone the build to take place at a time when I am not working at the machine, or
when the work/cpu load is really low.
Thus, it would be useful if there was a way to schedule builds to take place at a later time.
This could be based on certain factors, i.e. system load (reading directly from /proc or using
kde sensors).

- build priorities:

for users it would be useful to be able to configure priorities for each scheduled
build (high vs. low)

- build dependencies:

it is not unusual for developers to download a number of related tarballs which feature
mutual dependencies, thus for a software build manager it would make sense to provide
an abstract view of related tarballs, which may need to be configured/built in a certain
order, using information that may come from other projects. This would enable a scenario
where users may configure a number of tarballs to either "be" dependencies of another tarball,
or to provide dependencies to another tarball, so that kompile would be able to automatically
build related packages in a given order.

Again, thank you very much for an already very neat piece of software, and please consider the above ramblings only of advisory character, maybe other users could leave comments concerning these ideas, to help you assess what is generally considered useful and what isn't.

All the Best

--
dispatched
Reply to this

I can install it!

by forbore on: Apr 14 2008

Score 50%

forbore

I always get this error:

libtool: link: cannot find the library `/usr/lib/libfam.la'

I run Mandriva Powerpack 2008.0 64bit

Reply to this

Re: I can install it

by forbore on: Apr 14 2008

Score 50%

forbore

I tried running the RPM but nothing happens.

Reply to this

I have a problem

by baDibere on: Jul 24 2008

Score 50%

baDibere

I have downloaded stable version and I installed it (using ./configure, make, make install). But when I want to try to run it, an error shows and says :
"You have forgot to specify a valid sources tarball or specified file isn't a valid sources tarball!
Specify an existing and valid source tarball please.
Maual selection of sources tarball and building options manual setup will be avaiable in future version."

What does it mean? What's the problem and solution?

Thanks..

Reply to this

Re: I have a problem

by baDibere on: Jul 24 2008

Score 50%

baDibere

Ok.. No problem.

Reply to this

Errors When Compiling

by brando56894 on: May 6 2009

Score 50%

brando56894

Im trying to compile Kompile under arch linux 64 and I'm getting these errors:

main.cpp: In function ‘int main(int, char)’:
main.cpp:96: error: ‘exit’ was not declared in this scope
main.cpp:104: error: ‘exit’ was not declared in this scope
main.cpp:127: error: ‘exit’ was not declared in this scope
main.cpp:151: error: ‘exit’ was not declared in this scope
main.cpp:251: error: ‘exit’ was not declared in this scope
main.cpp:275: error: ‘exit’ was not declared in this scope
main.cpp:283: error: ‘exit’ was not declared in this scope
main.cpp:294: error: ‘exit’ was not declared in this scope
main.cpp:309: error: ‘exit’ was not declared in this scope
main.cpp:332: error: ‘exit’ was not declared in this scope
main.cpp:345: error: ‘exit’ was not declared in this scope
make[2]: * [main.o] Error 1
make[2]: Leaving directory `/home/bran/builds/kompile/src/kompile-0.3-beta3/src'
make[1]: * [all-recursive] Error 1
make[1]: Leaving directory `/home/bran/builds/kompile/src/kompile-0.3-beta3'
make: * [all] Error 2
==> ERROR: Build Failed.
Aborting...

Reply to this

goto page:

... 4 5 6 7 8 9 10 11 12

Add commentBack

Linux42.org

ask question
more

Popular Groups

Desktop Screenshots

Newest Groups

Elementary OS

Nahuatl language

FORUM

Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog

Explore
Apps
Artwork
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Content RSS
Events RSS

Participate
Groups
Forum
Add Content
Public API

About openDesktop.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse

Copyright 2007-2016 openDesktop.org Team
All rights reserved. openDesktop.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
openDesktop is a trademark of the openDesktop.org Team

All

Office

Multimedia

Graphic

Network

Printing

Text Editors

Education

Business

Telephony

Games

Development

Administration

Scientific

Security

Utilities

PDA Software

Server Software

Accessibility

Embedded

Libraries

Other Software

Documents

Social Desktop Contest

Kompile