"find_header" will be merged in the CVS HEAD.
I think this kind of change request should be post to comp.lang.ruby, or ruby-talk mailing list. not to RCR, since this is not the language change.
-- matz.
Specifically for my machine here (WinXP), the HEADER_SEARCH_PATH should be, abbreviated,
[ "C:\DXSDK\Include", "$(VCInstallDir)include", "$(VCInstallDir)atlmfc\include", "$(VCInstallDir)PlatfromSDK\include\prerelease", "$(VCInstallDir)PlatformSDK\include", "$(FrameworkSDKDir)include", "C:\Program Files\Creative Labs\OpenAL 1.0 SDK\Include" ]
p ENV["INCLUDE"] #=> [ "$(VCInstallDir)include", "$(VCInstallDir)atlmfc\include", "$(VCInstallDir)PlatfromSDK\include\prerelease", "$(VCInstallDir)PlatformSDK\include", "$(FrameworkSDKDir)include" ]
Also, the same machine (cygwin), the HEADER_SEARCH_PATH should be, abbreviated,
[ "$(cygwin_root)usr/include", "$(gcc_prefix)include" ]
p ENV["INCLUDE"] #=> [ "$(VCInstallDir)include", "$(FrameworkSDKDir)include" ]
Am I not sure how one would correct these situations. In neither case is the ENV perfectly accurate. In the former, everything in the DXSDK and OpenAL directories would be ignored, which would be devastating to anyone making a DirectX or OpenAL extension for Ruby. The PlatformSDK also contains previous versions of DirectX headers, bearing the same header file name as the DXSDK. Can the interpreter do any snooping to fix this?
-chemdog
"find_header" will be merged in the CVS HEAD.
I think this kind of change request should be post to comp.lang.ruby, or ruby-talk mailing list. not to RCR, since this is not the language change.
-- matz.
Specifically for my machine here (WinXP), the HEADER_SEARCH_PATH should be, abbreviated,
Also, the same machine (cygwin), the HEADER_SEARCH_PATH should be, abbreviated,
Am I not sure how one would correct these situations. In neither case is the ENV perfectly accurate. In the former, everything in the DXSDK and OpenAL directories would be ignored, which would be devastating to anyone making a DirectX or OpenAL extension for Ruby. The PlatformSDK also contains previous versions of DirectX headers, bearing the same header file name as the DXSDK. Can the interpreter do any snooping to fix this?
-chemdog