flavorjones / flavorjones/ruby-c-extensions-explained
Document trilogy's variation on the packaged_source strategy
Open
- Dominant language
- C
- Stars
- 115
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Trilogy concatenates all the packaged source into a single C file, see https://github.com/github/trilogy/blob/main/contrib/ruby/ext/trilogy-ruby/extconf.rb#L5
which is a notable variation from what we do with libyaml in https://github.com/flavorjones/ruby-c-extensions-explained/tree/main/packaged_source
Contributor guide
Research direction
Start with Trilogy's contrib/ruby/ext/trilogy-ruby/extconf.rb at line 5, then compare it with the libyaml packaged_source example in ruby-c-extensions-explained. Document how Trilogy concatenates packaged source into one C file and explain how that differs from the existing libyaml approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100