# Ruby-exiv2 EXIF handling library now usable

**URL:** <https://www.ruby-forum.com/t/ruby-exiv2-exif-handling-library-now-usable/81420>\
**Category:** Ruby\
**Created:** [January 9, 2007, 12:24am UTC](https://www.ruby-forum.com/t/ruby-exiv2-exif-handling-library-now-usable/81420 "2007-01-09T00:24:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![max-lapshin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c77e96/32.png) [@max-lapshin](https://www.ruby-forum.com/u/max-lapshin)\
**Post date:** [January 9, 2007, 12:24am UTC](https://www.ruby-forum.com/t/ruby-exiv2-exif-handling-library-now-usable/81420/1 "2007-01-09T00:24:06Z")

</div>

I’ve implemented extension to library exiv2 and created project on  
rubyforge: ruby-exiv2 long time ago. But there was a problem, that gem  
wasn’t installable. Extension compiled, but no bundle (dynamic library)  
remained.

Now, I’ve found the problem. I was keeping all .c files in subfolder  
lib, and included extension from this folder. When gem was being  
installed, make && make install && make clean was performed in subfolder  
lib. make install kept the compiled extension in lib folder and make  
clean deleted it. So, no extension left.

I’ve moved all source files to subfolder ext and now make install moves  
compiled extension out of the make clean hands. So, now you can use  
ruby-exiv2 library.