I remember doing something like this in extconf.rb:The mkmf gets the list of C source files to be used for the shared librar= y
from the current directory only.
Is this the only stupid way to list C source files for ruby extensions?
2009/2/3 Rados=B3aw Bu=B3at said:I remember doing something like this in extconf.rb:The mkmf gets the list of C source files to be used for the shared library
from the current directory only.
Is this the only stupid way to list C source files for ruby extensions?
$srcs =3D [
# c files listed here
]
$objs =3D [
# object files listed here
]
I looked at the mkmf sources and see that it use that global variables
but I don't know if there is better way. Btw. mkmf source is very
poor.. it would be nice to have better replacement for mkmf.
2009/2/4 Alex Katebi said:2009/2/3 Rados=B3aw Bu=B3at said:$srcs =3D [
# c files listed here
]
$objs =3D [
# object files listed here
]
I assume I should do something like $srcs =3D %w[../src/foo.c ../src/more= c]
Yes.
If I have some time in the future I will write an autoconf & automake
replacement for mkmf and give it to Matz. Ruby deserves better than this
mkmf hack.
Rados³aw Bu³at said:2009/2/4 Alex Katebi said:I assume I should do something like $srcs = %w[../src/foo.c ../src/more.c]2009/2/3 Rados³aw Bu³at said:$srcs = [
# c files listed here
]
$objs = [
# object files listed here
]
Yes.
If I have some time in the future I will write an autoconf & automake
replacement for mkmf and give it to Matz. Ruby deserves better than this
mkmf hack.
Ruby gives big possibility to build nice api and mkmf is just ugly
(both from programmer and source perspective).
Good luck!
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.