The Racket repository
76ab851d2a
To get the expected contents of the various environment variables, I used a similar approach to what the build does in `grab_batch_vars': * Start a cmd.exe shell (not a real shell) * Dump the env into a buffer * Run "... Studio/VC/vcvarsall.bat" (modifies envvars, which is why cmd is needed) * Dump new env into a new buffer * Sort both buffers and compare Hopefully it still works also on Matthew's setup. Two other small things: * Use ".obj" suffix on windows to avoid warning. * Catch error when trying to delete the .so file, since on the x86_64 machine it throws an error. (I'm not sure how it *doesn't* do that with the i386 machine.) |
||
|---|---|---|
| collects | ||
| doc | ||
| man/man1 | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| README | ||
The Racket programming language =============================== Important executables: * DrRacket: Racket's integrated development environment (start here!). * Racket: the main command-line entry point for running racket programs and scripts. * GRacket: the GUI-mode Racket executable. * raco: Racket's command-line toolset. More Information ---------------- Racket comes with extensive documentation: use DrRacket's `Help' menu, or run `raco docs'. Also, visit us at http://racket-lang.org/ for more Racket resources. Instructions for building Racket from source are in src/README. License ------- Racket Copyright (c) 2010-2012 PLT Scheme Inc. Racket is distributed under the GNU Lesser General Public License (LGPL). This means that you can link Racket into proprietary applications, provided you follow the rules stated in the LGPL. You can also modify Racket; if you distribute a modified version, you must distribute it under the terms of the LGPL, which in particular means that you must release the source code for the modified software. See doc/release-notes/COPYING.txt for more information.