autotools support

[Lorenzo Bettini]

I've been using

/trunk/playground/devtools/kdevelop4-extra-plugins/automake

as Robert told me...

Aleix Pol wrote:
> Looks like you're not using the trunk version, now the automake support 
> is in playground, not in kdevelop
> 
> On Sun, May 17, 2009 at 12:00 PM, Lorenzo Bettini <bettini at dsi.unifi.it 
> <mailto:bettini at dsi.unifi.it>> wrote:
> 
>     By the way, this is the modified CMakeList.txt, is that correct?
> 
>     macro_optional_add_subdirectory(cmake)
>     macro_optional_add_subdirectory(qmake)
>     macro_optional_add_subdirectory(custommake)
>     macro_optional_add_subdirectory(automake)
> 
> 
> 
>     Robert Gruber wrote:
> 
>         Hmm, I just did a complete rebuild. Removed both kdevelop und
>         kdevplatform's build directory and re-run cmake. All compiled fine.
> 
>         May you can try to remove your build directories and rebuild all?!
> 
> 
>         -------- Original-Nachricht --------
> 
>             Datum: Sat, 16 May 2009 21:07:29 +0200
>             Von: Lorenzo Bettini <bettini at dsi.unifi.it
>             <mailto:bettini at dsi.unifi.it>>
>             An: kdevelop-devel at barney.cs.uni-potsdam.de
>             <mailto:kdevelop-devel at barney.cs.uni-potsdam.de>
>             Betreff: Re: autotools support
> 
> 
>             Hi Robert
> 
>             I've just tried that but I get this error:
> 
>             Scanning dependencies of target kdevautomakeimporter_automoc
>             Generating moc_automakeimporter.cpp
>             /home/bettini/install/kdevelop/projectmanagers/automake/automakeimporter.h:52:
>             Error: Undefined interface
>             automoc4: process for
>             /home/bettini/install/kdevelop/build/projectmanagers/automake/moc_automakeimporter.cpp
>             failed: Unknown error
>             pid to wait for: 0
>             returning failed..
> 
>             in particular this line
> 
>             Q_INTERFACES( KDevelop::IBuildSystemManager )
> 
>             actually I rerun cmake and then make on an already compiled
>             kdevelop (in a separate build directory)...
> 
> 
> 
> 
>     -- 
>     Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
>     ICQ# lbetto, 16080134     (GNU/Linux User # 158233)
>     HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
>     http://www.myspace.com/supertrouperabba
>     BLOGS: http://tronprog.blogspot.com  http://longlivemusic.blogspot.com
>     http://www.gnu.org/software/src-highlite
>     http://www.gnu.org/software/gengetopt
>     http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
> 
> 
>     _______________________________________________
>     KDevelop-devel mailing list
>     KDevelop-devel at kdevelop.org <mailto:KDevelop-devel at kdevelop.org>
>     https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


-- 
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134     (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com  http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net