Recent changes to Home

Home modified by cyg Simple

cyg Simple — Fri, 14 Dec 2018 15:35:36 -0000

--- v4
+++ v5
@@ -2,8 +2,11 @@
 ## Why? ##
 What is the point of having a separate distribution of software dependent on Cygwin?  Basically the reason is that I find the setup experience to be combersome to use.  I looked at MSYS2 and their use of  [Arch Linux's pacman](https://www.archlinux.org/pacman/) system and thought that it would be useful for delivering Cygwin as well.  This concept should prove interesting depending on the number of users of this system I have.  Unlike MSYS2 I can use Cygwin's `ln -s` functionality and unlike MSYS2 I am doing more package spliting.  I am also doing static only builds unless the source packages forces the use of a DLL.

-## Static Only ##
+## Static Only Builds ##
 I also find the need for rebasing every DLL a bit of a challenge and there are still reports of collision during runtime.  Reducing the number of required  DLL to a minimum will help with the  collision issues.  It also helps with the aftershock of installing packages that need to be rebased, basically there should only be a few with the cygSimple scheme.  I still need to test the speed differences between static link versus dynamic link but from apperance I think the static linked coreutils is a bit faster.
+
+## DLL May Be Required ##
+Some libraries require a DLL and some have license issues for the end user if the library isn't used as a DLL.  For this reason alone libraries licensed under GPL will be delivered.  The binary executables cygSimple delivers will be staticly built instead of using those DLL.  For this to work packages that provide both libraries and executables require the PKGBUILD to build once as shared and then again as static.  Some libraries such as gmp for example require one or the other because the delivered headers are based on shared versus static build.  In these cases, for the time being, only the static version will be released.

 ## Status ##
 I am currently in the process of making things work.  This is a  chicken and egg process where I'm having to build the eggs to produce the chickens and to build some chickens to produce some eggs.  As I work out each item I will upload them to the file system in the packages and sources directories.  The source files contain the [makepkg](https://www.archlinux.org/pacman/makepkg.8.html) [PKGBUILD](https://www.archlinux.org/pacman/PKGBUILD.5.html) file, patch files and the upstream source file.  The makepkg program is part of the pacman package which I still need to upload so you'll need to wait on that.  I'll update this page once I have  pacman available to use.

Home modified by cyg Simple

cyg Simple — Sun, 25 Nov 2018 15:21:03 -0000

--- v3
+++ v4
@@ -11,4 +11,4 @@
 The wiki uses [Markdown](/p/cygsimple/wiki/markdown_syntax/) syntax.

 [[members limit=20]]
-[[download_button]]
+[ [download_button] ]

Home modified by cyg Simple

cyg Simple — Wed, 15 Aug 2018 14:52:57 -0000

--- v2
+++ v3
@@ -1,4 +1,12 @@
-The idea I have is to use Cygwin with a minimal set of files to be productive.  I will be creating a set of files that you can use on a USB thumb drive and be productive.  I will be sharing ideas for scripts to interface with native (i.e. not Cygwin dependent) applications such as a native VIM or native PERL.  The files I distribute will be in ZIP format since these are native to windows.  I am focusing on the x86_64 Windows OS but with enough detail that someone could use the information to create a x86 version as well and upload to this project for distribution.
+# cygSimple #
+## Why? ##
+What is the point of having a separate distribution of software dependent on Cygwin?  Basically the reason is that I find the setup experience to be combersome to use.  I looked at MSYS2 and their use of  [Arch Linux's pacman](https://www.archlinux.org/pacman/) system and thought that it would be useful for delivering Cygwin as well.  This concept should prove interesting depending on the number of users of this system I have.  Unlike MSYS2 I can use Cygwin's `ln -s` functionality and unlike MSYS2 I am doing more package spliting.  I am also doing static only builds unless the source packages forces the use of a DLL.
+
+## Static Only ##
+I also find the need for rebasing every DLL a bit of a challenge and there are still reports of collision during runtime.  Reducing the number of required  DLL to a minimum will help with the  collision issues.  It also helps with the aftershock of installing packages that need to be rebased, basically there should only be a few with the cygSimple scheme.  I still need to test the speed differences between static link versus dynamic link but from apperance I think the static linked coreutils is a bit faster.
+
+## Status ##
+I am currently in the process of making things work.  This is a  chicken and egg process where I'm having to build the eggs to produce the chickens and to build some chickens to produce some eggs.  As I work out each item I will upload them to the file system in the packages and sources directories.  The source files contain the [makepkg](https://www.archlinux.org/pacman/makepkg.8.html) [PKGBUILD](https://www.archlinux.org/pacman/PKGBUILD.5.html) file, patch files and the upstream source file.  The makepkg program is part of the pacman package which I still need to upload so you'll need to wait on that.  I'll update this page once I have  pacman available to use.

 The wiki uses [Markdown](/p/cygsimple/wiki/markdown_syntax/) syntax.

Home modified by cyg Simple

cyg Simple — Sun, 26 Oct 2014 16:19:42 -0000

--- v1
+++ v2
@@ -1,6 +1,4 @@
-Welcome to your wiki!
-
-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+The idea I have is to use Cygwin with a minimal set of files to be productive.  I will be creating a set of files that you can use on a USB thumb drive and be productive.  I will be sharing ideas for scripts to interface with native (i.e. not Cygwin dependent) applications such as a native VIM or native PERL.  The files I distribute will be in ZIP format since these are native to windows.  I am focusing on the x86_64 Windows OS but with enough detail that someone could use the information to create a x86 version as well and upload to this project for distribution.

 The wiki uses [Markdown](/p/cygsimple/wiki/markdown_syntax/) syntax.

Home modified by cyg Simple

cyg Simple — Wed, 22 Oct 2014 18:36:44 -0000

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Members:

cyg Simple (admin)