[Bug 82296] Gideon II: A separate configuration for KDevelp CVS

Amilcar do Carmo Lucas amilcar at ida.ing.tu-bs.de
Fri May 28 09:18:08 UTC 2004


------- 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=82296      
amilcar ida ing tu-bs de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From amilcar ida ing tu-bs de  2004-05-28 09:17 -------
Yes, two alternatives:

- We change a lot o code and create kdevelop_be (KDevelop bleeding edge) just like Quanta did. And Please do not mention the Gideon name never ever again.

- You create a new user (I use be) and add this to you .bashrc
export KDE_BE_DIR=/mnt/home/be/kde3
export KDEDIRS=$KDE_BE_DIR:/opt/kde3
export PATH=$KDE_BE_DIR/bin:$PATH
export LD_LIBRARY_PATH=$KDE_BE_DIR/lib:$LD_LIBRARY_PATH
Then make a cron job of the be user build and install the latest KDevelop every nigth (--prefix = /mnt/home/be/kde3) while you sleep using kdecvs-build or kdesdk/scripts/kde-build.

I use and prefer the second option.




More information about the KDevelop-devel mailing list