Ticket #11 (closed enhancement: fixed)

Opened 6 months ago

Last modified 5 months ago

Refactor extconf.rb

Reported by: raggi Assigned to: raggi
Priority: major Milestone: EventMachine "Framework"
Keywords: extconf, java Cc:

Description

Extconf has grown over the projects lifecycle, and with some more patches I have here for Mingw support, it'll be getting hard to follow and hard to manage.

I can see some very effective (and probably more portable) refactor possibilities.

In particular:

  • Base lib names on compiler name (windows / unix / mingw / cygwin split works much more effectively)
  • Refactor out repeated code
  • Checkout Rice for other ideas with the munging problem (if there are any others)
  • Add java here?

Due to the lack of all of the OSes in extconf (most are available), a small tool for validating the output would be useful. This could later be included in the test suite if appropriate.

Change History

06/03/08 15:10:58 changed by raggi

  • status changed from new to assigned.

Ok, it looks like we can go to just using Rake for everything.

This could have a number of advantages, so next stage is to try and translate it all into Rake.

06/30/08 20:01:38 changed by raggi

  • status changed from assigned to closed.
  • resolution set to fixed.