Difference between revisions of "GNUstep Installation Process"

From GNUstepWiki
Jump to navigation Jump to search
m (add link)
 
(13 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
Stefan Urbanek, please modify whatever you see fit, even delete this page.
+
At the moment, the ways available to install GNUstep is heavily dependent on the host operating system platform.  
  
−
GNUstep installation process should be and could be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms. Given GNUstep's cross-platform declaration on application development activities, so should the application mangement activies cross-platform united. But in oder to get there, following need to be done.
+
==Installing from source code==
  
−
GNUstep package creation automation project.
+
If you wish to install from source code, instructions are available from [http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto_toc.html GNUstep Howto] - and if you want to stay on the bleeding edge, check out point 7 on that page or Dennis Leeuw's [http://gnustep.made-it.com/BuildGuide/index.html GNUstep Build Guide for Unix Systems].
  
−
* What?: This is a project to automate the process of creating GNUstep environment for a perticular OS platform.
+
* latest instructions for [[Installation on Windows]]
 +
* latest instructions for [[Gorm Installation On Windows]]
 +
* latest instructions for [[Installation of 32bit GNUstep on 64bit Linux]]
  
−
* Why?:
+
==Using your native packaging system==
−
** Lots of time is spent by experienced GNUsteppers to assist new GNUsteppers with compiling the source, and this waste will continue to occur unless we resolve certain issues.
 
−
** Time can be better spent on GNUstep developement, and not on the compling and packaging process.
 
−
** Easy installation and removal of GNUstep encourges the deployment of GNUstep in corporate environments.
 
−
** The softare adn pacakge creation processes can be reproduced easliy by others with simple commands.
 
−
** Improves QA testing by generating GNUstep bug fixed instances quickly.
 
  
−
Plan
+
Many platforms offer native GNUstep packages that may be installed in the same way that other software is commonly installed. Some information on platform-specific packages can be located at [[Platform_compatibility]].
  
−
* Introduce CPAM(Cross-Platform Application Management) tool implemented by TWW Inc. to GNUstep CPAD community
+
==Some aspirations==
−
** Cross-Platform is easier said then done becuase each platform's features are barriers for others.
 
  
−
* Release GNUstep package source implemented by TWW CPAM.
+
GNUstep installation process could be and should be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms.  
−
** I will release a working package source for others to try and review.  
 
−
** The package soruces can generate native package format for RHAS rpm,Solaris pkgadd and HP-UX depot formats.  
 
  
−
* Write tutorial on learning TWW CPAM.
+
Given GNUstep's cross-platform approach to application development activities, the application mangement activies should also be united across OS platforms.
−
** I am willing to help/assist a few persons to get familliar with TWW tools if they promise to write up what they learned in a tutorial article. As you can see I am really not good on documenation work.
 
  
−
* Integrate GNUstep developement process with TWW CPAM.
+
For "pkg-inst GNUstep-1.0" details, please see [[Package_management]].
  
−
 
 
−
* More details TBA once I get familiar with mediawiki.
 
  
−
* Following lines can be deleted later.
+
Few notes: http://lists.gnu.org/archive/html/discuss-gnustep/2005-01/msg00381.html
−
  I just want to make above out of nohere text not treated as spam.
 
−
  My name is T.J. Yang(tj_yang at hotmail dot com),
 
−
  I have been working as a system administator and I am interested
 
−
  to bring the CPAM experience to work on this project. I promised myslef to digitalize the
 
−
  compiling process when "Adam Fedor" was kindly answer my emails regarding to the compiling issues
 
−
  I econcuntered.
 
−
 
−
  Please email me if you have comment/questions.
 
−
  For detail about TWW, please see http://www.thewrittenword.com.
 
−
  I have used CPAM tool at work to bring cross-platform open-source software support
 
−
  nightmare under control. TWW CPAM tool is battle field tested ;)
 
−
 
 
−
  All the TWW tools and sources of their supported packages are GPL open-source compliant.
 
−
  They are freely avaiable(ftp://support.thewrittenword.com) but support labor and binary packages are not.
 

Latest revision as of 11:07, 29 October 2006

At the moment, the ways available to install GNUstep is heavily dependent on the host operating system platform.

Installing from source code

If you wish to install from source code, instructions are available from GNUstep Howto - and if you want to stay on the bleeding edge, check out point 7 on that page or Dennis Leeuw's GNUstep Build Guide for Unix Systems.

Using your native packaging system

Many platforms offer native GNUstep packages that may be installed in the same way that other software is commonly installed. Some information on platform-specific packages can be located at Platform_compatibility.

Some aspirations

GNUstep installation process could be and should be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms.

Given GNUstep's cross-platform approach to application development activities, the application mangement activies should also be united across OS platforms.

For "pkg-inst GNUstep-1.0" details, please see Package_management.


Few notes: http://lists.gnu.org/archive/html/discuss-gnustep/2005-01/msg00381.html

Retrieved from "https://mediawiki.gnustep.org/index.php?title=GNUstep_Installation_Process&oldid=3859"