cb9289bd0b
The distro-build process creates an executable in a build area, then uses it to set up a distribution in a "bundle" directory. That way, any package-supplied native libraries will be found in the process of installaning a package, in case installation needs native libraries. Don't switch in the case of cross-compiling, though. For cross-compilation, `PLAIN_RACKET` still has to be used, since it is set up to be one that runs on the build platform, and the `PLAIN_RACKET` installation simply has to have any needed native libraries installed. That's why the makefile wasn't using the exectuable in "bundle" before for package installation (but it can create trouble for non-cross builds, especially on Windows). |
||
|---|---|---|
| pkgs | ||
| racket | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| appveyor.yml | ||
| azure-pipelines.yml | ||
| INSTALL.txt | ||
| Makefile | ||
| README.md | ||
This is the source code for the core of Racket. See "INSTALL.txt" for full information on building Racket.
To build the full Racket distribution from this repository, run make
in the top-level directory. To build minimal Racket, run make base.
The rest of the Racket distribution source code is in other repositories, mostly under the Racket GitHub organization.
Contribute to Racket by submitting a pull request, joining the development mailing list, or visiting the IRC channel.
License
Racket is distributed under the GNU Lesser General Public License (LGPL). This implies that you may 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 states that you must release the source code for the modified software.
See racket/src/COPYING_LESSER.txt for more information.