Re: [ ruby-Bugs-9604 ] mkmf find_header doesn't modify compiler include path in generated Makefile

[e-mail] wrote:
> Bugs item #9604, was opened at 2007-03-26 22:09
> You can respond by visiting: 
> http://rubyforge.org/tracker/?func=detail&atid=1698&aid=9604&group_id=426
> 
> Category: Standard Library
> Group: None
> Status: Open
> Resolution: None
> Priority: 3
> Submitted By: Riley Lynch (rlynch)
> Assigned to: Nobody (None)
> Summary: mkmf find_header doesn't modify compiler include path in generated Makefile
> 
> Initial Comment:
> The doc for find_header reads in part:
> 
>   If the header is found then the path it was found on is added to the list
>   of included directories that are sent to the compiler (via the -I switch).
> 
> However, although the search is correctly performed, it does not appear to affect the Makefile output. The implementation of find_header (around line 640 in mkmf.rb for ruby 1.8.4) reads in part:
> 
>   if try_cpp(cpp_include(header), opt)
>     $INCFLAGS << " " << opt
>     found = true
>     break
>   end
> 
> However, $INCFLAGS does not appear in the "configuration" method which generates the Makefile text. ($CPPFLAGS does, however.)
> 
> Compare find_library, which augments LIBS and LIBPATH in the Makefile if the corresponding library is found.

Works for me as advertised on Solaris 10 with Ruby 1.8.6. I stuck a 
test.h file in my home directory and ran extconf.rb over it.

# In the extconf.rb file
find_header('test.h', '/export/home/djberge')

# In the Makefile
$INCFLAGS = -I. -I$(topdir) -I$(hdrdir) -I$(srcdir) -I/export/home/djberge

What I *think* may have tricked you is that it doesn't use an absolute 
path, so if you do this:

find_header('test.h', Dir.pwd)

Then extconf.rb will merely turn that into another "-I.", instead of 
giving you the expanded path. Is that what happened?

Regards,

Dan