mirror of
https://github.com/rust-lang/rust.git
synced 2026-04-27 18:57:42 +03:00
reorg
+3
@@ -9,3 +9,6 @@ When you're done with a bikeshed topic, please either abandon it or move it to a
|
||||
* [[Bikeshed constrained types]]
|
||||
|
||||
## Abandonned
|
||||
|
||||
* [[Bikeshed extracted documentation]]
|
||||
* [[Bikeshed disjoint union types]]
|
||||
|
||||
+5
-1
@@ -9,7 +9,7 @@ Listing of documentation for users:
|
||||
|
||||
## Wiki Documents
|
||||
|
||||
###
|
||||
### General instructions for users
|
||||
|
||||
* [[Doc getting started]]
|
||||
|
||||
@@ -18,3 +18,7 @@ Listing of documentation for users:
|
||||
* [[Doc language FAQ]]
|
||||
* [[Doc project FAQ]]
|
||||
* [[Doc usage FAQ]]
|
||||
|
||||
### Old or disorganized instructions
|
||||
|
||||
* [[Doc old getting started]]
|
||||
+9
-2
@@ -1,4 +1,7 @@
|
||||
Listing of minutes from weekly meetings:
|
||||
|
||||
Listing of minutes from meetings:
|
||||
|
||||
## Weekly meetings:
|
||||
|
||||
* [[Meeting weekly 2011-10-11]] (unsafe blocks; typestate; tutorial; destructuring)
|
||||
* [[Meeting weekly 2011-10-18]] (status update)
|
||||
@@ -8,4 +11,8 @@ Listing of minutes from weekly meetings:
|
||||
* [[Meeting weekly 2011-12-06]] (status update)
|
||||
* [[Meeting weekly 2011-12-13]] (no implicit copies; unique closures; type classes; libraries)
|
||||
* [[Meeting weekly 2011-12-20]] (varieties of function; semicolon syntax)
|
||||
* [[Meeting weekly 2012-01-03]] (new syntax; blocks vs for loops; interfaces; rustbot)
|
||||
* [[Meeting weekly 2012-01-03]] (new syntax; blocks vs for loops; interfaces; rustbot)
|
||||
|
||||
## In-person meetings:
|
||||
|
||||
* [[Meeting inperson 2011-04-06]] (kind system; resources; env capture)
|
||||
|
||||
@@ -1,25 +0,0 @@
|
||||
# Environment Setup
|
||||
1. Install the [[Mozilla-Build enviornment|http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe]] (referred to as m-b)
|
||||
2. Install [[Git|http://msysgit.googlecode.com/files/Git-1.7.3.1-preview20101002.exe]]
|
||||
* In the installer, don't have git autoconvert line endings. Just use a good text editor like vim or emacs.
|
||||
3. Add the Git path to the PATH environment variable used by the m-b environment. m-b likes to reset the PATH when it starts you'll want to edit %USERPROFILE%/.bash_profile (~/.bash_profile if you're in the m-b environment). The m-b default shell is bash 3.1.
|
||||
* For git, add the Git/cmd directory instead of the Git/bin directory to avoid any conflicts with the existing tools in the m-b environment.
|
||||
5. In m-b's /bin/ directory (or somewhere on your path), you'll want to add a script named 'git' which will invoke the CMD.exe shell script which was installed in step 3:
|
||||
```python
|
||||
#!python
|
||||
import os
|
||||
import subprocess
|
||||
import sys
|
||||
|
||||
path = "%s\Git\cmd\git.cmd" % os.environ['PROGRAMFILES']
|
||||
|
||||
cmdline = [path]
|
||||
cmdline.extend(sys.argv[1:])
|
||||
|
||||
git = subprocess.Popen(cmdline)
|
||||
|
||||
sys.exit(git.wait())
|
||||
```
|
||||
6. You should now be able to run `git` and `ocaml` directly from the shell
|
||||
7. Apply my as-yet-unposted patches
|
||||
8. `make check`
|
||||
+1
-1
@@ -1,4 +1,4 @@
|
||||
The github wiki system is generally good but Suffers from a couple weak points.
|
||||
The github wiki system is generally good but suffers from a couple weak points.
|
||||
|
||||
* No built-in category, tagging or namespace system
|
||||
* No search
|
||||
|
||||
+5
-2
@@ -1,17 +1,19 @@
|
||||
Listing of Notes for developers:
|
||||
Listing of notes for developers:
|
||||
|
||||
## Process and workflow notes
|
||||
|
||||
* [[Note wiki conventions]]
|
||||
* [[Note development roadmap]]
|
||||
* [[Note compiler snapshots]]
|
||||
* [[Note git workflow]]
|
||||
|
||||
## Language notes
|
||||
## Language and implementation notes
|
||||
|
||||
* [[Note interfaces]]
|
||||
* [[Note attributes]]
|
||||
* [[Note defined attributes]]
|
||||
* [[Note tasks and communication]]
|
||||
* [[Note metadata format]]
|
||||
|
||||
## Library notes
|
||||
|
||||
@@ -21,3 +23,4 @@ Listing of Notes for developers:
|
||||
## Miscellaneous notes
|
||||
|
||||
* [[Note constraints in rustc and libraries]]
|
||||
* [[Note seeing LLVM output from rust]]
|
||||
|
||||
+1
@@ -14,6 +14,7 @@ Listing of proposals:
|
||||
|
||||
* [[Proposal for unique types]]
|
||||
* [[Proposal for interfaces]]
|
||||
* [[Proposal for logging]]
|
||||
|
||||
## Withdrawn
|
||||
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
Note: This information is out of date and tinderbox is no longer our preferred build automation
|
||||
|
||||
Running a tinderbox is very simple:
|
||||
|
||||
* Get a rust build environment working first. Like, get your own system through 'make check'
|
||||
* `hg clone http://hg.mozilla.org/users/graydon_mozilla.com/rust-tinderbox`
|
||||
* `cd rust-tinderbox`
|
||||
* `vi rust-tinderbox.py`:
|
||||
* edit `smtpserver` to some working SMTP relay you can send mail through
|
||||
* edit `username` to your email address (if you want to; it controls who you're sending email 'From')
|
||||
* `./rust-tinderbox.py`
|
||||
|
||||
From time to time you might also want to run `hg pull -u` to get fresher tinderbox code as we adjust it; it changes slowly but it will happen from time to time. Join IRC to ask if the scripts stop working.
|
||||
Reference in New Issue
Block a user