| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This was introduced in commit a7c113e580c1565000166f9967da82ff2ecdaeaa to avoid interference with host build.
However it prohibits setting important flags for cross-build.
Also don't force 'LDFLAGS=-pipe -s' in configure, which doesn't work with clang targeting MacOS.
It can now be set externally.
|
|
|
|
|
|
|
| |
Rubies can be build like so:
rake-compiler cross-ruby VERSION=2.7.0:2.6.0 HOST=x86_64-w64-mingw32:i686-w64-mingw32
This builds the cross product of all ":" separated ruby and host versions.
To force sequential builds add option "-j1".
|
|
|
|
| |
Starting from 3.0.0-preview2, Ruby stopped shipping tar.bz2 archives.
This changes the archive format to tar.gz for better compatibility.
|
|
|
|
|
|
| |
The .so files of extensions are often manually stripped after compilation per task in a Rakefile.
This is done to reduce gem size and because debug information in release binaries isn't particular useful.
This manual step can be avoided, if the cross ruby version is built with stripping enabled.
Compatibility is ensured, since stripping files a second time doesn't make a difference.
|
|
|
|
|
| |
ALT_SEPARATOR doesn't exist in Makefile.in since Ruby 1.9.2:
https://github.com/ruby/ruby/commit/7c7690045870396816624bf57775eb29e6a478fd
|
|
|
|
|
|
| |
GitHub: fix #161
Reported by Masaki Hara. Thanks!!!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The extension libraries of the ruby stdlib are not required to cross build
binary gems. They just waste compilation time and disk storage.
The option "--with-ext=" is supported since ruby-1.9.2, but ruby-1.8.7 just
ignores this option. I verified that the cross ruby-build and building binary
gems succeeds with the following ruby versions:
``` sh
rake-compiler cross-ruby VERSION=1.8.7-p374 HOST=i586-mingw32msvc
rake-compiler cross-ruby VERSION=1.9.3-p550 HOST=i586-mingw32msvc
rake-compiler cross-ruby VERSION=2.0.0-p645 HOST=i686-w64-mingw32
rake-compiler cross-ruby VERSION=2.0.0-p645 HOST=x86_64-w64-mingw32
rake-compiler cross-ruby VERSION=2.1.6 HOST=i686-w64-mingw32
rake-compiler cross-ruby VERSION=2.1.6 HOST=x86_64-w64-mingw32
rake-compiler cross-ruby VERSION=2.2.2 HOST=i686-w64-mingw32
rake-compiler cross-ruby VERSION=2.2.2 HOST=x86_64-w64-mingw32
```
The options '--without-tk' and '--without-tcl' are obsolete since ruby 1.8.7.
I already use this patch as part of the [rake-compiler-dock](https://github.com/larskanis/rake-compiler-dock) .
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It's not moved yet but it will be done soon.
|
|
|
|
|
|
|
|
|
|
| |
Attempt to please old Debian/Ubuntu that ships 1.9.3 with RubyGems
1.8.23, making impossible to install rake-compiler on it.
Also since Debian/Ubuntu disables `gem update --system`, those users
had not workaround to it.
Closes #93
|
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
Rely on CDN instead of direct access to Ruby-Lang FTP mapping and
take advance of some speedups.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 0.9.0 the support for usage of x86-mingw32 platforms was removed for
cross-compile platforms.
In the wild, several gems use this syntax to indicate the platforms the
gem targets.
Since this is a massive breakage, a workaround need be put in place.
This change restores that functionality and accept also the
RUBY_PLATFORM one (i386-mingw32)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
It was trying to include Isolate file that no longer exists.
Including Gemfile instead.
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
| |
This platform is binary compatible with i386-mingw32 and is used
to keep compatibility with VC6/MSVCRT.dll builds of Ruby.
`-60` refers to the MSVCRT version (6.0) used by Visual C 6.0 back
in the day, even that today real version is 7.x
Other builds of Ruby with Visual C uses a different version of
MSVCRT.dll (8.0, 9.0 10.0) and because of that, are not binary
compatible with this.
|
|
|
|
| |
1.8.7-p371 has been quite stable ;-)
|
| |
|
|\
| |
| | |
Add support for cross builds for multiple target platforms.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also prefix the selection of rbconfig in config.yml with the corresponding
Ruby platform.
This allowes to use cross compiled Ruby-builds for multiple target
architectures on the same machine. This is especially usefull to compile
for Ruby-2.0 i386-mingw32 and x64-mingw32 platforms.
|
|/
|
|
|
| |
- Ruby 1.8.7 (while EOL is June 2003)
- RubyGems 1.8.25
|
| |
|
| |
|
|
|
|
|
|
|
| |
Environment variables like CC, CXX, LDFLAGS, CPPFLAGS and RUBYOPT
might be leaking from user's environment or tools like Bundler.
Unset those to avoid these alter the cross-compilation of Ruby.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Isolate default installation is tmp... Now I remember.
|
| |
|