From: Eric MSP Veith <eveith@...>
Date: 2010-11-13T02:24:46+09:00
Subject: [ruby-core:33154] Using Ruby's C API safely and sanely

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Rubyists!

I'm trying to integrate Ruby (both for bindings and embedded interpreter) 
into a larger project, namely RPM 5. I'm facing a diffuclty here 
and hope that somebody might point out a more elegant way of solving things.

The problem is that including the ruby.h file leads to the inclusion of 
Ruby's config.h file. This is clearly not appreciated, as we need to cope 
with a lot of HAVE_FOO_H defines, or even Ruby's PACKAGE_NAME, etc. 
definitions which of course override RPM's. Is there a sane way of using 
Ruby's C API, i.e. including the Ruby header file, without having Ruby wreak 
havok on our own defines?

Thanks alot in advance. Every hint is greatly appreciated.

			Eric

P. S. I have already posted a similar message to Ruby-Talk. It contained 
another question, which has been answeren by now. For the config.h issue, 
however, I'm still in need of some advice.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkzYI6wACgkQhS0drJ3goJJVPwCeO/DMR6sGbg777cfjBrwoz8f/
GNcAn1fvmTOkwzXOgNHhzS7u8FkStJ0s
=KNRE
-----END PGP SIGNATURE-----