Are there any other not complete CMakeLists.txt traps waiting?
Look in my build scripts, near the top of each, for whether I have the AUTOTOOLS variable enabled:
applications/amarok/amarok.SlackBuild -> I use autotools applications/dolphin/dolphin.SlackBuild -> I use autotools applications/konversation/konversation.SlackBuild applications/kpilot/kpilot.SlackBuild -> I use autotools applications/tde-systemsettings/tde-systemsettings.SlackBuild -> I use autotools tde-i18n/tde-i18n.SlackBuild tdeaddons/tdeaddons.SlackBuild tdemultimedia/tdemultimedia.SlackBuild -> I use autotools tdenetwork/tdenetwork.SlackBuild tdesdk/tdesdk.SlackBuild tdetoys/tdetoys.SlackBuild tdeutils/tdeutils.SlackBuild tdewebdev/tdewebdev.SlackBuild -> I use autotools
Here is what I am building with cmake:
Side note:
tde-knetworkmanager9 -> this is for HAL systems, otherwise use
tdenetworkmanager
tde-kpowersave-> ditto, use tdepowersave
Darrell
On 02/02/2014 12:35 PM, Darrell Anderson wrote:
Side note:
tde-knetworkmanager9 -> this is for HAL systems, otherwise use
tdenetworkmanager
tde-kpowersave-> ditto, use tdepowersave
Yes,
Those are not being built/installed, those PKGBUILD scripts all reside in the development directory regardless :)
Yes, I have to do a rename and copy on the fly to move PKGBUILD-tde-name to the correct build directory under PKGBUILD, but there is no better way to develop 100 build files simultaneously than to open them all and have them at your fingertip in kate -- and have the terminal window available to rsync the updates to the build server in mass :)
Look:
http://www.3111skyline.com/dl/dt/trinity/ss/kate-efficiency.jpg
-
Darrell Anderson -
David C. Rankin