[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-commits
Subject: [emerge] /: Update readme
From: Hannah von Reth <vonreth () kde ! org>
Date: 2016-06-20 9:26:07
Message-ID: E1bEvT5-00031H-2a () code ! kde ! org
[Download RAW message or body]
Git commit 2d0518d0692488cf0b61157cdcd46f9054bd62cd by Hannah von Reth.
Committed on 20/06/2016 at 09:25.
Pushed by vonreth into branch 'master'.
Update readme
D +0 -113 README
A +9 -0 README.md
http://commits.kde.org/emerge/2d0518d0692488cf0b61157cdcd46f9054bd62cd
diff --git a/README b/README
deleted file mode 100644
index 064a496..0000000
--- a/README
+++ /dev/null
@@ -1,113 +0,0 @@
-This is the readme for the emerge scripts to build kde on windows.
-
-contents:
-1. step-by-step guide
-2. emerge options
-3. the environment and the directory layout
-4. remarks to the step-by-step guide
-5. Authors, Contact and License
-
-1. step-by-step guide
- - Get Python >= 2.7 ( e.g. from http://www.python.org ).
- - If you can read this file you probably already got the svn-sources.
- If not, get an svn client, preferrably TortoiseSVN ( from
- http://tortoisesvn.net/downloads ).
- - If you have not done already: make up a directory kderoot somewhere;
- We will refer to it as %KDEROOT% or just kderoot - the name is not
- important at all though.
- - Put another directory emerge into %KDEROOT% enter that directory
- and checkout from svn://anonsvn.kde.org/home/trunk/kdesupport/emerge .
- - Add another directory etc to %KDEROOT%. Copy the file
- kdesettings-example.bat from the emerge directory into the etc
- directory. Rename kdesettings-example.bat to kdesettings.bat and edit it
- according to your needs.
- - open up kdeenv.bat from the emerge directory, try 'emerge -p kdebase-runtime'
- and if there are no errors, you can use emerge.
-
-2. running emerge
-Call "emerge --help" to get the current documentation
-how to call emerge, its recognized commands and options.
-(Alternatively open emerge.py in your text editor to read the same text.)
-
-3. the environment and the directory layout
-For running emerge in a preset environment, please use the kdeenv.bat. this
-will set all Environment variables for you that are needed to build KDE4.
-Please be aware that cygwin shouldn't be in your path.
-KDE on windows uses a special layout that might change in future releases.
-Below %KDEROOT% you will find common unix folders such as bin, lib and etc.
-There are some special folders that have another meaning though:
-\emerge This folder contains the portage directory, the emerge scripts
- within the folder bin, this README and the kdesettings-example.bat
-\tmp This folder contains the build directories of all packages.
- After finishing with emerge, you can empty this folder.
-\etc this folder contains lots of settings.
-\bin Contains all executables and all shared libraries.
-\lib Contains all non-shared libraries.
-\include Contains header files.
-\share Contains lots of additional stuff: Wallpapers,mimetype definitions
- and some more.
-\mingw This folder only exists if you install mingw or gdb with emerge.
- The kdeenv.bat will include this folder into the path for you.
- You can of course use this compiler outside of KDE as well.
-
-4. remarks to the step-by-step guide
-
-Python should be within your path ( which is normally set automatically ).
-You don't have to register python with the file ending .py though the author
-of these lines finds it useful.
-
-
- - If you can read this file you probably already got the git sources.
- If not, get an git client, preferrably TortoiseGit ( from
- http://code.google.com/p/tortoisegit ).
-
-TortoiseGit is an extension to the Windows Explorer and a full featured git
-client. It makes development easy. The point in not using a commandline client
-is that emerge will not check for an installed commandline client yet.
-
-
- - If you have not done already: make up a directory kderoot somewhere;
- We will refer to it as %KDEROOT% or just kderoot - the name is not
- important at all though.
-
-As already stated the name isn't really important. Currently all KDE files
-will be installed under KDEROOT, but this might change in the future.
-
-
- - Put another directory emerge into %KDEROOT% enter that directory
- and clone from git://anongit.kde.org/emerge .
-
-If you want to directly work on emerge itself, please clone from git@git.kde.org:emerge
-instead.
-
-
- - Add another directory etc to %KDEROOT%. Copy the file
- kdesettings-example.bat from the emerge directory into the etc
- directory. Rename kdesettings-example.bat to kdesettings.bat and edit it
- according to your needs.
-
-The file kdesettings-example.bat should contain all necessary informations.
-You should read at that point.
-
-
- - open up kdeenv.bat from the emerge directory, try 'emerge -p kdebase'
- and if there are no errors, you can use emerge.
-
-You will get a list of packages that emerge would try to build.
-You can most of the time ignore warning messages - they are mostly for your
-information.
-
-5. Authors, Contact and License
-There were multiple authors working on these scripts:
-Holger Schr�der
-Patrick Spendrin
-Christian Ehrlicher
-Jaroslaw Staniek
-Shane King
-Bernhard Reiter
-Ralf Habacker
-
-You can contact us via our mailing list kde-windows@kde.org
-
-License: the file portage_versions.py can be used
-under GPLv2 all other files are licensed (if needed) under BSD
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..b0d22a8
--- /dev/null
+++ b/README.md
@@ -0,0 +1,9 @@
+# Getting in Touch
+
+IRC: [#kde-windows](irc://irc.freenode.net/kde-windows)
+Mailing list: kde-windows@kde.org
+
+# Links
+
+[Website](https://community.kde.org/Windows)
+[Report Bugs] (https://phabricator.kde.org/project/profile/61/)
\ No newline at end of file
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic