[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 119601] New: Use LD_PRELOAD for KParts Projects to avoid to have to install every time
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-01-05 23:38:43
Message-ID: 20060106003841.119601.joachim.eibl () gmx ! de
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=119601         
           Summary: Use LD_PRELOAD for KParts Projects to avoid to have to
                    install every time
           Product: kdevelop
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: NEW
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: joachim.eibl gmx de


Version:            (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
OS:                Linux

When writing a big program for KDE then the installation via "make install" can take \
up a lot of time. But I have to install  everytime after compiling, or otherwise KDE \
(KTrader) doesn't use my kparts-so-file. My solution is to use the \
environmentvariable LD_PRELOAD in the runtime settings of the project for debugging \
within kdevelop. Example:
LD_PRELOAD=/home/joachim/kdiff3-0.9.89/debug/src/.libs/libkdiff3part.so

Even if KTrader now finds another version of the library, my private version will be \
used because the dlopen()-function is forced to use the already loaded version.

My suggestion is that the kdevelop-project-properties support the LD_PRELOAD in such \
a way that no absolute path is necessary. The project-properties-runtime-options \
could get an extra tab "Preloaded libraries" that allows to specify the so-files to \
preload relative to the executable file in the build-directory. The wizard for new \
projects could then setup a KPart-project to use this preload feature.

This would already be a great help (also for newbies). Yet I also want to mention two \
related issues. When ui-rc-files or the XML-documentation changes, I still have to \
reinstall, although this happens much less often. Here I think that kdevelop needs \
some help by KDE. Similar to the LD_PRELOAD-environment variable some variables to \
add search directories for ui-rc-files and documentation would be helpful. (e.g.: \
"KDE_UIRC_DIRS", "KDE_DOC_DIRS". Or does something similar already exist?)

The goal is to allow a user to develop and test his/her application without \
installing it, even if it contains several libraries. The main advantage would be \
that an already existing version of the same program wouldn't be disturbed during \
development and stays useful and reliable. And the (newbie-) programmer doesn't have \
to know a root-password or details about installation etc.

Cheers,
Joachim


[prev in list] [next in list] [prev in thread] [next in thread]