You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way libxml2 expects to be used when installed from source is that you call 'xml2-config --cflags --libs' and it outputs the flags needed to pass to GCC so it can find its headers and libraries. That's why libxml2 puts its stuff under 'libxml2/libxml', so even if you install to /usr or /usr/local, you still have to use this to get the header locations.
If Nokogiri used xml2-config to get the locations of the headers/libraries, then many installations of libxml2 would suddenly start working without having to pass in custom header or library file locations when building the Nogokiri gem.
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
The way libxml2 expects to be used when installed from source is that you call 'xml2-config --cflags --libs' and it outputs the flags needed to pass to GCC so it can find its headers and libraries. That's why libxml2 puts its stuff under 'libxml2/libxml', so even if you install to /usr or /usr/local, you still have to use this to get the header locations.
If Nokogiri used xml2-config to get the locations of the headers/libraries, then many installations of libxml2 would suddenly start working without having to pass in custom header or library file locations when building the Nogokiri gem.
Thanks
The text was updated successfully, but these errors were encountered: