Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Integrate libbel #22

Closed
abargnesi opened this issue Feb 8, 2015 · 2 comments
Closed

Integrate libbel #22

abargnesi opened this issue Feb 8, 2015 · 2 comments
Assignees
@abargnesi

Comments

@abargnesi
Copy link
Member

The libbel C library is currently used on bel.rb's next branch however it does not build with the gem.

Build libbel with the bel.rb gem for linux, mac osx, and windows.
@abargnesi abargnesi self-assigned this Feb 8, 2015
@abargnesi abargnesi added the ready label Feb 8, 2015
abargnesi pushed a commit that referenced this issue Feb 8, 2015
added libbel as submodule at vendor/libbel
a449dc5 
refs #22
abargnesi pushed a commit that referenced this issue Feb 8, 2015
build libbel on gem install
6a695ee 
what is working:
- libbel builds using autools
- bel gem picks up libbel.so
- BEL::Completion api works

problems:
- make clean doesn't properly clear some build files. this is a problem
  with the Makefile.am settings in libbel.
- requires ragel for gem installation

refs #22
abargnesi added a commit that referenced this issue Feb 9, 2015
@abargnesi
cp libbel.so to lib/libbel.so; FFI load via path
73b454b 
the libbel.so library had to be added to the loadpath for bel.rb.

libbel.so path is calculated relative to the lib_bel.rb source file.

refs #22
@abargnesi
Copy link
Member Author

Work to build libbel C library happens on gem install. The libbel.so library is then loaded via the bel.rb load path (lib/libbel.so).

I have not yet integrated the rake-compiler tasks to compile for all platforms, but that will be next.

@abargnesi abargnesi mentioned this issue Mar 6, 2015
Closed
@abargnesi abargnesi mentioned this issue Apr 13, 2015
Open
@abargnesi
Copy link
Member Author

Integrated in 0.3.0 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@abargnesi abargnesi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abargnesi