So, I have fixed one problems and uncovered another.  I finally got gtest fixed upstream in Homebrew, which involved patching gtest-config for Homebrew.  The problem was that gtest-config --libs would return a file like &quot;/usr/local/lib/<a href="http://libgtest.la">libgtest.la</a>&quot; which was being stripped because .la files shouldn&#39;t be used on the mac.  This was due to the way gtest-config look at the directories it was installed to.  For those that don&#39;t know Homebrew installs all packages into a container folder called a &quot;Keg&quot; which are all stored in the &quot;Cellar&quot;, like so: &quot;/usr/local/Cellar/gtest/1.5.0/&lt;stuff&gt;&quot;.  Then Homebrew symlinks the appropriate files to /usr/local/{lib,include,bin,share,etc...}.  <div>

<br></div><div>So, now gtest-config properly returns -lgtest now instead of the file path, but something else changed.  Before the patch gtest-config --includedir returned &quot;/usr/local/include&quot;, but now returns &quot;/usr/local/Cellar/gtest/1.5.0/include&quot;.<div>

<br></div><div>So why does this matter?  Well this general -I/usr/local/include was covering another issue.  Once this had changed in gtest-config, roslib couldn&#39;t find boost headers anymore... This is because rosboost-cfg wasn&#39;t returning anything for `rosboost-cfg --include_dirs`, as the boost install was detected to be a &quot;ver.is_system_install&quot;.  </div>

<div><br></div><div>So why is /usr/local/include not in there by default?  This is because the -isysroot command is used to point to the MacOSX10.7.sdk, which does not have a symlink to /usr/local/include in it.  That means to compile anything that uses boost (or anything else that has headers in /usr/local/include) now I have to add -I/usr/local/include manually.</div>

<div><br></div><div>tl;dr:</div><div><br></div><div>I need to add -I/usr/local/include to the c++ arguments when compiling something with boost (but more generally it should be a system default include).  How should that be accomplished?</div>

<div><ul><li>Should the rosboost-cfg --include_dirs return that?  (currently it doesn&#39;t because it detects the Homebrew boost as being &quot;system installed&quot; and returns &quot;&quot;)</li><ul><li><a href="https://code.ros.org/trac/ros/browser/stacks/ros/tags/ros-1.6.2/tools/rosboost_cfg/src/rosboost_cfg/rosboost_cfg.py#L250">https://code.ros.org/trac/ros/browser/stacks/ros/tags/ros-1.6.2/tools/rosboost_cfg/src/rosboost_cfg/rosboost_cfg.py#L250</a></li>

<li>This implys that the larger issue should be fixed by each individual library with headers in /usr/local/include</li></ul><li>Should &quot;/usr/local/include&quot; be added to the CPLUS_INCLUDE_PATH in something like .bashrc?</li>

<li>Some other strategy?</li></ul><div>Just wanted to get some others input.</div></div><div><br></div><div>Thanks,</div><div><br clear="all">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>William Woodall<br>Graduate Software Engineering<br>

Auburn University<br><a href="mailto:w@auburn.edu" target="_blank">w@auburn.edu</a><br><a href="mailto:wjwwood@gmail.com" target="_blank">wjwwood@gmail.com</a><div><a href="http://williamjwoodall.com" target="_blank">williamjwoodall.com</a><br>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><br>
</div></div>