Issues - luislavena/rake-compiler

luislavena / rake-compiler

Description:

Provide a standard and simplified way to build and package Ruby C and Java extensions using Rake as glue.

Sort by: Priority | Votes | Last Updated

Loading…

4.

0 votes

Feature
x

Allow parameter passing to extconf
0 comments Created 7 months ago by luislavena

Title

Body
Right now the only way to feed parameters to `extconf` is using `config_options`. This imposes some hardcoded paths. ideally `rake compile` or `rake cross compile` should be able to accept parameters after double dashes, like `gem install` does.
or cancel

Right now the only way to feed parameters to extconf is using config_options. This imposes some hardcoded paths. ideally rake compile or rake cross compile should be able to accept parameters after double dashes, like gem install does.

Comments

Parsed with GitHub Flavored Markdown
9.

0 votes

Feature
x

Building fat gems for macosx and linux
2 comments Created 2 months ago by banister

Title

Body
it is currently possible to build fat gems for windows, but not yet for macosx or linux. It would nonetheless be a handy feature if we could build fat gems for macosx/linux especially for macosx where not all users have devtools installed (and so do not have a C compiler). using the rvm gem might be one way to manage this build process.
or cancel

it is currently possible to build fat gems for windows, but not yet for macosx or linux. It would nonetheless be a handy feature if we could build fat gems for macosx/linux especially for macosx where not all users have devtools installed (and so do not have a C compiler).

using the rvm gem might be one way to manage this build process.

Comments

visionmedia Thu Oct 01 11:32:38 -0700 2009 | link

gcc ships with the mac os no?

Comment
gcc ships with the mac os no?
or cancel

banister Thu Oct 01 11:42:56 -0700 2009 | link

no, you must first install devtools or xcode

Comment
no, you must first install devtools or xcode
or cancel

Parsed with GitHub Flavored Markdown
12.

0 votes

Feature
x

"rake cross compile" doesn't choose correct g++ executable
3 comments Created about 1 month ago by lylejohnson

Title

Body
I'm working with the latest rake-compiler (post-0.6.0) from GitHub and it seems that while the "rake cross compile" task does correct set the C compiler (to "i586-mingw32msvc-cc" on my machine) it doesn't get the C++ compiler right (it chooses plain old "g++" instead of "i586-mingw32msvc-g++"). I'm looking into this and will provide a patch if I figure it out; just wanted to get it recorded somewhere.
or cancel
I'm working with the latest rake-compiler (post-0.6.0) from GitHub and it seems that while the "rake cross compile" task does correct set the C compiler (to "i586-mingw32msvc-cc" on my machine) it doesn't get the C++ compiler right (it chooses plain old "g++" instead of "i586-mingw32msvc-g++"). I'm looking into this and will provide a patch if I figure it out; just wanted to get it recorded somewhere.

Comments
luislavena Tue Oct 27 14:21:01 -0700 2009 | link

Thank you Lyle

This is actually not a rake-compiler issue, but the lack of rbconfig to setup CXX.

rake-compiler uses rbconfig in combination with mkmf. rbconfig was generated by miniruby during the build process, and lacks that information.

The only place rake-compiler defines the compiler itself is here:

http://github.com/luislavena/rake-compiler/blob/master/lib/rake/extensioncompiler.rb

And the only purpose is to help determine the platform and the executable for manual execution.

But this is not used by mkmf or the cross compile process at all.

I advice you setup an environment variable or a extconf parameter that let you assign the CXX properly.

I advice against using ExtensionCompiler to define that in extconf (since the gem will not be available in that particular version of the cross-compiled ruby).

Comment
Thank you Lyle This is actually not a rake-compiler issue, but the lack of rbconfig to setup CXX. rake-compiler uses rbconfig in combination with mkmf. rbconfig was generated by miniruby during the build process, and lacks that information. The only place rake-compiler defines the compiler itself is here: http://github.com/luislavena/rake-compiler/blob/master/lib/rake/extensioncompiler.rb And the only purpose is to help determine the platform and the executable for manual execution. But this is not used by mkmf or the cross compile process at all. I advice you setup an environment variable or a extconf parameter that let you assign the CXX properly. I advice against using ExtensionCompiler to define that in extconf (since the gem will not be available in that particular version of the cross-compiled ruby).
or cancel
lylejohnson Tue Oct 27 14:27:28 -0700 2009 | link
OK, I understand. Trying now with:

rake cross compile CXX=/usr/bin/i586-mingw32msvc-g++

and that seems to be working a little better (so far!)
Comment
OK, I understand. Trying now with: rake cross compile CXX=/usr/bin/i586-mingw32msvc-g++ and that seems to be working a little better (so far!)
or cancel
luislavena Tue Oct 27 14:29:14 -0700 2009 | link

Good news.

Feel free to create a patch then that extend ExtensionCompiler to define the g ++ executable for the mingw host.

Comment
Good news. Feel free to create a patch then that extend ExtensionCompiler to define the g ++ executable for the mingw host.
or cancel

Parsed with GitHub Flavored Markdown
7.

0 votes

Feature
x

Stand-alone?
3 comments Created 4 months ago by trans

Title

Body
I'd like to rake-compiler independently of Rake. What do yo think of forking rake-compiler and building a stand-alone tool (one that could still offer a rake-task of course)?
or cancel

I'd like to rake-compiler independently of Rake. What do yo think of forking rake-compiler and building a stand-alone tool (one that could still offer a rake-task of course)?

Comments

luislavena Thu Aug 13 05:44:44 -0700 2009 | link

rake-compiler has been built around Rake and the task dependency chain, porting it to standalone mode would require a lot of work to ensure build process do not get mistakenly fired.

There is Tap also, but until now noone has proven me how to use it for file-based task as replacement of Rake.

I'm not going to stop you explore that way, and if you succeed, would happily integrate it.

Comment
rake-compiler has been built around Rake and the task dependency chain, porting it to standalone mode would require a lot of work to ensure build process do not get mistakenly fired. There is Tap also, but until now noone has proven me how to use it for file-based task as replacement of Rake. I'm not going to stop you explore that way, and if you succeed, would happily integrate it.
or cancel

trans Thu Aug 13 11:46:34 -0700 2009 | link

okay. then I might fork your project and see how far I can get in doing it. what is Tap? do you know where can I find more info on it? thanks.

Comment
okay. then I might fork your project and see how far I can get in doing it. what is Tap? do you know where can I find more info on it? thanks.
or cancel

luislavena Thu Aug 13 11:48:12 -0700 2009 | link

http://tap.rubyforge.org/

Comment
http://tap.rubyforge.org/
or cancel

Parsed with GitHub Flavored Markdown
13.

0 votes

rake-compiler JavaExtensionTask should provide sanity check when there is no compilation
0 comments Created 8 days ago by myabc

Title

Body
To reproduce, create a basic project structure. mkdir ext/my_java_extension And create a blank `.java` file (`MyJavaExtensionService.java`) in the above directory. Create a Rakefile with the following: Rake::JavaExtensionTask.new('my_java_extension') `javac` will not complain about being passed a blank `.java` file, but will not emit a `.class` file. `jar` will then be passed zero file arguments and output an error/usage message.
or cancel
To reproduce, create a basic project structure.
```
mkdir ext/my_java_extension
```
And create a blank .java file (MyJavaExtensionService.java) in the above directory.

Create a Rakefile with the following:
```
Rake::JavaExtensionTask.new('my_java_extension')
```
javac will not complain about being passed a blank .java file, but will not emit a .class file. jar will then be passed zero file arguments and output an error/usage message.
Comments

Parsed with GitHub Flavored Markdown