Talk:Installing third party softwares in terminal/Build/KDE4/Windows - Revision history

Praneethu.u: moved Talk:Getting Started/Build/KDE4/Windows to Talk:Installing third party softwares in terminal/Build/KDE4/Windows: I want to know how to install a 3rd party software , which doesn't have 1-click install. eg. i downloaded pidgin and extract

2011-02-02T02:09:28Z

moved Talk:Getting Started/Build/KDE4/Windows to Talk:Installing third party softwares in terminal/Build/KDE4/Windows: I want to know how to install a 3rd party software , which doesn't have 1-click install. eg. i downloaded pidgin and extract

Rhabacker: msvc debug/relase mixing problem

2007-09-18T10:09:40Z

msvc debug/relase mixing problem

Rhabacker: added gdb notes

2007-09-18T09:42:16Z

added gdb notes

Rhabacker: kdelibs/kde application state

2007-09-17T06:07:55Z

kdelibs/kde application state

Tampakrap: added msi evaluation, added debus merge problems

2007-09-16T19:52:55Z

added msi evaluation, added debus merge problems

Tampakrap: cmake, kdewin-installer issues

2007-09-16T13:06:18Z

cmake, kdewin-installer issues

Tampakrap: fixed numbering

2007-09-16T12:40:55Z

fixed numbering

Tampakrap: dbus notes

2007-09-16T12:39:30Z

dbus notes

Jstaniek at 10:41, 16 September 2007

2007-09-16T10:41:58Z

Jstaniek: /* KDE-Windows Meeting: Notes */

2007-09-16T10:39:34Z

‎KDE-Windows Meeting: Notes

← Older revision		Revision as of 10:09, 18 September 2007
Line 48:		Line 48:
	#compiler tools chain issues		#compiler tools chain issues
	#* loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.		#* loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
		+	#* There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

@@ Line 46: / Line 46: @@
 #* umbrello - writing and printing does not work
 #* ...
+#compiler tools chain issues

@@ Line 37: / Line 37: @@
 #**integrity checks (md5 package and file checks)
 #**cd/dvd/usb stick installation
 === KDE on Windows can be called the first official KDE-own distribution ===

@@ Line 23: / Line 23: @@
 #*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
 #*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
 #dbus for win32 is working mostly for recent kde applications, although there are some issues:
 #*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
-#*if dbus-daemon is killed the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
+#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
 #*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
-#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verifed with qdbusviewer.
+#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
-#*There is some open work to merge the windows port into the dbus cvs.
+#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
-# There are some win32 issues with the cmake build system (TODO: list the issues)
+# win32 issues with the cmake build system (TODO: list the issues)
-# the kdewin-installer needs some additional features:
+# install system topics:
-#*update function
+#* it is planned to evaluate the microsoft windows installer for releasing kde windows application.
-#*simplified end user interface
+#* if msi is not usable the kdewin-installer should be extended with the following features:
-#*integrity checks (md5 package and file checks)
+#**update function
-#*cd/dvd/usb stick installation
+#**simplified end user interface
 === KDE on Windows can be called the first official KDE-own distribution ===

@@ Line 30: / Line 30: @@
 #*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verifed with qdbusviewer.
 #*There is some open work to merge the windows port into the dbus cvs.
 === KDE on Windows can be called the first official KDE-own distribution ===

← Older revision		Revision as of 10:41, 16 September 2007
Line 1:		Line 1:
−	~~==KDE-Windows Meeting: Notes==~~	+	{{improve}}

		+	==KDE-Windows Meeting: Notes==
	Started: [[User:Jstaniek\|jstaniek]] 11:40, 15 September 2007 (CEST)		Started: [[User:Jstaniek\|jstaniek]] 11:40, 15 September 2007 (CEST)

@@ Line 17: / Line 17: @@
 #*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
 #format of the kde mirrors:
+=== KDE on Windows can be called the first official KDE-own distribution ===
-=== KDE on Windows is the first official KDE-own distribution ===