Projects/KDE on Windows/Packaging - Revision history

Tfry: Add link to qt deployment info page

2013-01-11T17:42:38Z

Add link to qt deployment info page

Tfry: Less confusing headers

2013-01-11T17:38:44Z

Less confusing headers

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:31Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:49:02Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:49, 29 June 2011
			
Line 76:
Line 76:
    
  * Use   * Use
− <code>[mingw32-]make install DESTIR=Some\temporary\folder</code> + <syntaxhighlight lang="text">[mingw32-]make install DESTIR=Some\temporary\folder</code>
  * Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).   * Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).



Aheinecke: Hint to the nsis package base and remove one, nsis bashing opinion.
2011-02-22T10:55:10Z
Hint to the nsis package base and remove one, nsis bashing opinion.

				
				
				
				
			
			← Older revision
			Revision as of 10:55, 22 February 2011
			
Line 116:
Line 116:
    
  * Considerable effort to create and maintain the installer   * Considerable effort to create and maintain the installer
− * NSIS code is ugly! Danger of burning your eyes. Peek at it through your fingers, never look at it directly.  
    
  === Procedure ===   === Procedure ===
    
  + * There is a NSIS package base in emerge that can be used to generate a NSIS package directly from emerge. For examples on NSIS packaging check the emerge/portage/package files.
  * For documentation on NSIS, see http://nsis.sourceforge.net .   * For documentation on NSIS, see http://nsis.sourceforge.net .
  * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .   * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .



SommerLuk: Grouping the articles
2010-11-28T12:06:48Z
Grouping the articles

				
				
				
				
			
			← Older revision
			Revision as of 12:06, 28 November 2010
			
Line 1:
Line 1:
− = Packaging / Distributing KDE applications for Windows = + = Packaging / Distributing KDE applications for Windows – Overview =
−   + 
− == Overview == + 
    
  Currently, several approaches exist towards packaging KDE applications for Windows, and we will try to outline each approach and the steps involved. Which approach (or approaches) you chose will depend on the type of your application, and your personal taste. The main benefits and drawbacks of each approach are listed in the respective sections.   Currently, several approaches exist towards packaging KDE applications for Windows, and we will try to outline each approach and the steps involved. Which approach (or approaches) you chose will depend on the type of your application, and your personal taste. The main benefits and drawbacks of each approach are listed in the respective sections.
    
  Note that the approaches are not mutually exclusive, and in particular it is probably always a good idea to provide an emerge script.   Note that the approaches are not mutually exclusive, and in particular it is probably always a good idea to provide an emerge script.
  + 
  + 
  + = Compile from source =
    
  == Emerge ==   == Emerge ==
Line 30:
Line 31:
  Take a look at the existing emerge scripts in portage. Probably there is already a project with a similar setup, so you can copy most things.   Take a look at the existing emerge scripts in portage. Probably there is already a project with a similar setup, so you can copy most things.
    
  + 
  + = Repository based =
    
  == KDE windows installer ==   == KDE windows installer ==
Line 58:
Line 61:
  # Profit   # Profit
    
  + == Quick and dirty pack ==
  + 
  + You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.
  + 
  + === Advantages ===
  + 
  + * Should be real easy for you create.
  + 
  + === Disadvantages ===
  + 
  + * You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing in the correct directory, etc.
  + 
  + === Procedure ===
  + 
  + * Use
  + <code>[mingw32-]make install DESTIR=Some\temporary\folder</code>
  + * Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).
  + 
  + 
  + = As stand-alone application =
    
  == Installation bundle ==   == Installation bundle ==
Line 99:
Line 122:
  * For documentation on NSIS, see http://nsis.sourceforge.net .   * For documentation on NSIS, see http://nsis.sourceforge.net .
  * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .   * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .
−  
−  
− == Quick and dirty pack ==  
−  
− You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.  
−  
− === Advantages ===  
−  
− * Should be real easy for you create.  
−  
− === Disadvantages ===  
−  
− * You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing the the correct directory, etc.  
−  
− === Procedure ===  
−  
− * Use  
− <code>[mingw32-]make install DESTIR=Some\temporary\folder</code>  
− * Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).  



Tfry: /* Quick an dirty pack */ typo
2010-11-05T11:52:12Z
‎Quick an dirty pack:  typo

				
				
				
				
			
			← Older revision
			Revision as of 11:52, 5 November 2010
			
Line 101:
Line 101:
    
    
− == Quick an dirty pack == + == Quick and dirty pack ==
    
  You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.   You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.



Tfry: Add another quick-and-dirty option
2010-11-05T11:51:51Z
Add another quick-and-dirty option

				
				
				
				
			
			← Older revision
			Revision as of 11:51, 5 November 2010
			
Line 99:
Line 99:
  * For documentation on NSIS, see http://nsis.sourceforge.net .   * For documentation on NSIS, see http://nsis.sourceforge.net .
  * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .   * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .
  + 
  + 
  + == Quick an dirty pack ==
  + 
  + You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.
  + 
  + === Advantages ===
  + 
  + * Should be real easy for you create.
  + 
  + === Disadvantages ===
  + 
  + * You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing the the correct directory, etc.
  + 
  + === Procedure ===
  + 
  + * Use
  + <code>[mingw32-]make install DESTIR=Some\temporary\folder</code>
  + * Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).



Tfry: /* Packaging KDE applications for Windows */
2010-06-09T20:16:17Z
‎Packaging KDE applications for Windows

				
				
				
				
			
			← Older revision
			Revision as of 20:16, 9 June 2010
			
Line 1:
Line 1:
− = Packaging KDE applications for Windows = + = Packaging / Distributing KDE applications for Windows =
    
  == Overview ==   == Overview ==



Tfry: Add basic content
2010-06-09T20:14:44Z
Add basic content

				
				
				
				
			
			← Older revision
			Revision as of 20:14, 9 June 2010
			
Line 8:
Line 8:
    
  == Emerge ==   == Emerge ==
  + 
  + [[Getting_Started/Build/KDE4/Windows/emerge | Emerge]] allows to build KDE, and assorted other software on Windows from source, very easily. If you are developing KDE apps on Windows, you are probably familiar with it, already (and if you are not, you better take a look). Emerge also forms the basis for package building for the [[#KDE windows installer]].
    
  === Advantages ===   === Advantages ===
  + 
  + * Allows building from source, easily
  + ** Users can use different compilers / settings
  + * Excellent for developers and power users
  + * Basis for KDE windows installer packages
    
  === Disadvantages ===   === Disadvantages ===
  + 
  + * Compilation takes a long time
  + * Not really suited for end-users
  + * Compilation is broken at times ([http://winkde.org/pub/kde/ports/win32/dashboard/ latest build status])
    
  === Procedure ===   === Procedure ===
  + 
  + {{Improve|Does documentation exist? Write it/link it!}}
  + 
  + Take a look at the existing emerge scripts in portage. Probably there is already a project with a similar setup, so you can copy most things.
    
    
  == KDE windows installer ==   == KDE windows installer ==
  + 
  + The [[Projects/KDE_on_Windows/Installation|KDE windows installer]] is the officially recommended way for end-users to install the KDE SC, in whole or in part.
    
  === Advantages ===   === Advantages ===
  + 
  + * Full package management, including various packages, sources, headers.
  + * Includes update capabilities
  + * Downloads / installs only what is needed
  + * Great if user wants to install a whole collection of KDE apps.
    
  === Disadvantages ===   === Disadvantages ===
  + 
  + * Centralized? If your package is not part of the official KDE SC, you'll have to nag someone to get it into the installer.
  + * More complex than most other windows installers.
  + ** Arguably too complex for some end users.
  + ** Cumbersome esp. if user wants to install only one specific KDE app.
  + * Needs internet connection
    
  === Procedure ===   === Procedure ===
  + 
  + {{Improve|Does documentation exist? Write it/link it!}}
  + 
  + # Write an emerge script for your app
  + # ???
  + # Profit
    
    
  == Installation bundle ==   == Installation bundle ==
  + 
  + KDE on windows is self-contained, i.e. does not rely on the registry, or installed components outside of the main installation directory. This means you can simply zip a KDE installation (including your app) and let the user download and unzip on their system.
    
  === Advantages ===   === Advantages ===
  + 
  + * Easy to package
  + * Easy to install in a single step
  + * Can use a specific setup, including specific version of KDE, specific compiler, customized default settings, etc.
    
  === Disadvantages ===   === Disadvantages ===
  + 
  + * Need to offer/distribute sources!
  + * Wastes download size, and disk storage, if user want more than just one KDE application.
  + * No easy way to update / extend KDE installation.
    
  === Procedure ===   === Procedure ===
  + 
  + {{Improve|Properly list the steps from that mail, and the comments from the thread in this section.}}
  + 
  + See http://lists.kde.org/?l=kde-windows&m=127499109727979&w=2 .
    
    
  == Custom (NSIS) installer ==   == Custom (NSIS) installer ==
  + 
  + Of course developers can create a fully custom installer for their app, e.g. based on [http://nsis.sourceforge.net NSIS].
    
  === Advantages ===   === Advantages ===
  + 
  + * Can potentially cover all situations, if sufficiently refined
    
  === Disadvantages ===   === Disadvantages ===
  + 
  + * Considerable effort to create and maintain the installer
  + * NSIS code is ugly! Danger of burning your eyes. Peek at it through your fingers, never look at it directly.
    
  === Procedure ===   === Procedure ===
  + 
  + * For documentation on NSIS, see http://nsis.sourceforge.net .
  + * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .

← Older revision		Revision as of 17:42, 11 January 2013
Line 124:		Line 124:
	* For documentation on NSIS, see http://nsis.sourceforge.net .		* For documentation on NSIS, see http://nsis.sourceforge.net .
	* One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .		* One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .
		+
		+
		+	= Further info =
		+	* [http://qt-project.org/doc/qt-4.8/deployment-windows.html Deploying a Qt Application on Windows] (qt-project.org)

← Older revision		Revision as of 11:52, 5 November 2010
Line 101:		Line 101:


−	== Quick an dirty pack ==	+	== Quick and dirty pack ==

	You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.		You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.

← Older revision		Revision as of 11:51, 5 November 2010
Line 99:		Line 99:
	* For documentation on NSIS, see http://nsis.sourceforge.net .		* For documentation on NSIS, see http://nsis.sourceforge.net .
	* One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .		* One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 .
		+
		+
		+	== Quick an dirty pack ==
		+
		+	You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.
		+
		+	=== Advantages ===
		+
		+	* Should be real easy for you create.
		+
		+	=== Disadvantages ===
		+
		+	* You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing the the correct directory, etc.
		+
		+	=== Procedure ===
		+
		+	* Use
		+	<code>[mingw32-]make install DESTIR=Some\temporary\folder</code>
		+	* Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).

← Older revision		Revision as of 20:16, 9 June 2010
Line 1:		Line 1:
−	= Packaging KDE applications for Windows =	+	= Packaging / Distributing KDE applications for Windows =

	== Overview ==		== Overview ==