[gobolinux-users] KDE/QT related compiles failing

[Fábio Mierlo]

Some thing like a script that do the follow, will not work?

RunWith -p Qt 3.3.7 -p Glibc 2.3.2 -p Python  2.4.1 Compile KDE 3.5.6

and then

RunWith -p Qt 3.3.7 -p Glibc 2.3.2 -p Python  2.4.1 startkde/startx

This script can read from a runwith.conf file:

[KDE 3.5.6]
StrictDependsOf=Qt 3.3.7,Glibc 2.3.2,Python  2.4.1
RunComands=starx,startkde,Compile KDE 3.5.6

and will just update the environment variables
exactly like SymlinkProgram link in /System/Links:

PATH=/Programs/Qt/3.3.7/{bin,sbin}:/Programs/Glibc/2.3.2/{bin/sbin}:$PATH
LD_LIBRARY_PATH=/Programs/Qt/3.3.7/lib:/Programs/Glibc/2.3.2/lib:$LD_LIBRARY_PATH
C_INCLUDE_PATH=/Programs/Qt/3.3.7/include:/Programs/Glibc/2.3.2/include:$C_INCLUDE_PATH
PYTHONPATH=/Programs/Python/2.4.1/lib/python2.4/site-packages:$PYTHONPATH
...
. ModifyEnvironment Qt 3.3.7 # Replace Current by version 3.3.7
. ModifyEnvironment Glibc 2.3.2 # Replace /System/Links by /Program/Glibc/2.3.2
. ModifyEnvironment Python 2.4.1

ldconfig #optional?

Compile KDE 3.5.6/starkde/startx

Can it run automatically with LD_PRELOAD library?

On 7/7/07, hisham.hm at gmail.com <hisham.hm at gmail.com> wrote:
> On 7/6/07, Anshuman Aggarwal <anshuman at brillgene.com> wrote:
> > I had found the same link using the power of google earlier ...my german
> > is about the same as yours so that's what I had tried but with no luck...
> > the configure script was still using the current moc
> > I used the actual path of the moc bin from the 3.3.7 version
> > --with-qt-moc=/Programs/Qt/3.3.7/bin/moc
> >
> > I did have Qt4 installed and symlinked as the current one...
> >
> > It is working with Qt 3.3.7 symlinked (temporarily) ...but I was
> > wondering about the Compile level fix for this (and similar problems)?
> > Even though the dependency claims Qt < 4? Is this a problem that Compile
> > is not respecting the BuildInformation/BuildDependency?
>
> You hit a tricky issue, dependencies on executables. The dependency
> system assumes that a needed program being present under /Program is
> enough. It does not check if it is really symlinked. When working with
> the live system, there's really no way to solve this problem, as it is
> not safe to have Compile resymlink stuff for a build. Using
> ChrootCompile that's not a problem, as only the needed dependencies
> are inserted in the chroot, but that's still not as userfriendly as
> Compile. Eventually, Compile's behavior should evolve to default into
> something like running ChrootCompile --local-programs (which builds a
> safe chroot but uses entries from /Programs).
>
> -- Hisham
> _______________________________________________
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>