--with-sqlite3-include option doesn't take precedence over system libraries

[danfinnie]

Hi,

I'm running into an issue where the system sqlite3 libraries were not compiled with some compilation flags that I want. I tried to specify a --with-sqlite3-dir option to include my own version, but it was ignored for the system header files/libraries.

This behavior is documented in Ruby bug 9760 and Nokogiri accepted a patch to change this behavior. What do you think about doing something similar for sqlite3?

[danfinnie]

One downside to doing the patch from Nokogiri is that when that patch was accepted to Nokogiri, it seemed like a temporary fix until mkmf.rb was "fixed." But now, based on the Ruby bug, it seems like it will not be fixed as the Nokogiri patch assumes.

[luislavena]

@danfinnie do you experience the same behavior when using -- --with-opt-dir instead of sqlite3-dir?

[danfinnie]

@luislavena I just spent some time trying --with-opt-dir instead of --with-sqlite3-dir. That definitely made it use my header file over the system header file. I still couldn't make it use my dynamic library over the system one, though. I'm not too confident in if I was naming the library correctly and such though, so I wouldn't worry too much about it.

What I ended up doing was creating a fork of the sqlite3 gem that does not attempt to dynamically link sqlite3. I just copied in the sqlite3 source and header files.

I'm going to close this because I found a workaround and this is really a mkmf bug IMHO.