From: Jim Weirich Date: 2005-01-19T21:14:38+09:00 Subject: Re: Rubygems, native ruby extensions (and their dependencies) On Wednesday 19 January 2005 03:41 am, Johan Nilsson wrote: > - How should I handle native ruby extensions (building them at install time > is not an option here). Part of the library is implemented natively (Win32 > for now). I released my first binary gem yesterday. What I did: I compiled the gem software locally on my own machine. Then used the same gemspec I used for the source distribution with the following changes: (1) removed the extension (2) added the arch directory in the lib list (3) included the .so file in the list of included files. It seems to be working. It is the x10-cm17a gem for the windows platform if anyone is interested in trying it. The rake task for building gems is broken with regard to binary gems. I'll fix that for the next rake release. > - How should I handle the native ruby extensions' dependencies (e.g. > myrubyext.dll depends on boost-regex-...dll)? Where would such files go[1]? There is a requirements field in the gemspec that where you can list the dependencies. This is for comment purposes only, we don't do autodetection of non-gem dependencies. > - [a bit off-topic] Should/could I install applications through RubyGems as > well? Any special considerations with regards to application-specific > configuration files, invoking the application etc. Ideally I'd just like > the user to be able to run from the > command line after installation. I've released applications as gems. Rake is a prime example. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)