-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 15 January 2004 23:55, Alexander Kellett wrote:
> On Thursday 15 January 2004 22:02, George Staikos wrote:
> > On Thursday 15 January 2004 13:00, Stanislav Karchebny wrote:
> > > CVS commit by karchebny:
> > >
> > > * Per David Faure's suggestion
> > >  (http://lists.kde.org/?l=kde-core-devel&m=107393090622950&w=2)
> > >
> > >
> > >   M +1 -1      configure.in.in   1.40
> > >
> > >
> > > --- kdenonbeta/configure.in.in  #1.39:1.40
> > > @@ -1,3 +1,3 @@
> > > -#MIN_CONFIG(3.0)
> > > +#MIN_CONFIG(3.2)
> > >  # Define a symbol, to know that we're compiling WITH kde. (for apps
> > > that #  can compile without KDE, optionally)
> >
> >    And now developers who develop apps that are not ready for
> > kdeextragear or other modules, and who run KDE 3.1, cannot develop from
> > kdenonbeta anymore without patching configure.in.in.
>
> several apps in kdenonbeta itself are broken already due to this though.
> i'm assuming its not possible to make this per directory?
> if not. ./configure option?


David said that application that want to be runnable on KDE 3.0/3.1 should 
place a #MIN_CONFIG in their own directory. But to be exact, he said:

"Remove the (3.0) from kdenonbeta's own configure.in.in, and let apps who want
to run on 3.0, ship their own configure.in.in (when packaged out of 
kdenonbeta)."


Andras

>
> Alex

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFABxznTQdfac6L/08RAh1sAJ9d64IUAJ93rCYQHx/pmka5n2FDLgCfashs
cgTKHdpa83yNEwI8Odw3XEE=
=nUJn
-----END PGP SIGNATURE-----