[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: KDE/kdevelop/buildtools/builders/cmakebuilder
From: Aleix <aleixpol () gmail ! com>
Date: 2007-08-17 0:40:04
Message-ID: 757d9a550708161740o65a1b8cdqbdc998fed36897c1 () mail ! gmail ! com
[Download RAW message or body]
Hi Andreas,
Yes, you are right. I already thought about that, I will clean it up
as soon as I can :), for the moment, I have something that is working
more or less :).
Thanks,
Aleix
On 8/11/07, Andreas Pakulat <apaku@gmx.de> wrote:
> On 11.08.07 02:03:51, Aleix Pol Gonzalez wrote:
> > + KConfigGroup group(cfg.data(), "CMake");
> > +
> > + m_cmakeBinary = group.readEntry("CMake Binary", KUrl( "file:///usr/bin/cmake" ) );
> > + m_buildDirectory = group.readEntry("Build Dir");
> > + m_installPrefix = group.readEntry("Prefix");
> > + m_buildType = group.readEntry("Build Type", "-1");
> > +// return m_cmakeBinary.isEmpty() || m_buildDirectory.isEmpty();
> > + return true;
>
> I'm not very fond of storing such state information in plugins that
> operate on each project. Yes I know you're regenerating it for each
> build() call, but then you can as well save the bytes and just return a
> QMap or give prepared information to this function and then execute the
> process directly from here with the information read from the KConfig.
>
> Andreas
>
> --
> You will always get the greatest recognition for the job you least like.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel@kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic