On 23/06/2009 03:16, Ralf Habacker wrote: > nice to hear that there are ongoing efforts :-)
I just checked into Ports SVN a snapshot of my .cygport's and patches for KDE 4.2.4, so now you can see what I've done: http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/kde/ As for packaging, I've almost got kdelibs figured out; the rest is nowhere near finished. > It is possible to give related tools a different name on the cygwin > platform. > > In the kde buildsystem the variable KDE4_KCFGC_EXECUTABLE (located in > kdelibs/cmake/modules/FindKDE4Internals.cmake) contains the name of the > config compiler. > > The executable name of the config compiler could be changed in > kdelibs\kdecore\kconfig_compiler\CMakeLists.txt by adding an OUTPUT_NAME > property. That much I was aware of, but it's more than just that: 1) kdelibs/CONFLICTS lists 4 more, and omitted one, which are marked "devel only, doesn't matter [if they collide]". * checkXML: a simple script for invoking `meinproc{,4} --check`. Is this used by either automated build system, or is this only invoked manually? Are meinproc 3 & 4 compatible? * ksvgtopng: moved to kdebase-runtime; used for what? * kunittestmodrunner: probably don't need this for KDE3 anymore? * makekdewidgets: also renameable with KDE4_MAKEKDEWIDGETS_EXECUTABLE? * preparetips: exactly the same in 3.5 and 4.2; used for what? Are there any more? 2) The link libraries (e.g. libkdecore.dll.a) still collide. Changing LIB_INSTALL_DIR isn't an option, because then things like strigi analyzers and the like aren't installed in the correct place. Would changing just the ARCHIVE DESTINATION in INSTALL_TARGETS_DEFAULT_ARGS (as a Ports-specific patch) be an option? I'm not sure what else that might break. Yaakov ------------------------------------------------------------------------------ _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
