John Maddock ha escrito:
Folks, I have a configuration problem I don't know how to solve, so I'm soliciting for ideas.
[...]
So... in response to a bug-report I recently changed it to method 2 (on Linux anyway), using the same configuration logic as STLport to determine what "some_directory" is called. Having tested it locally with several gcc versions on Linux everything seemed fine... except it's not: the problem is that gcc has a configuration option that lets you change the name of the directory the headers go in, and several Linux distro's change it from the default, so instead of being the normal default of something like "4.2.0" it's g++-v4 or something else that we can't automatically deduce :-(
Obviously I could add a user-config macro for this purpose, but it's all a real pain basically :-(
Anyone any better ideas? Or should I give up before I loose the will to live ! ;-)
Have you asked at the STLport developers list (http://sourceforge.net/forum/forum.php?forum_id=490892 )? They have long tackled the same problem and their expertise can help. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo