Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project. It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Finally, speak up if you're already using mkrf or have played with it.
I'm happy to hear criticism.
I hope this thread can give me a list of things to work on as I try to
move the project along.
Is it a replacement for a tool like rake? If not how easy would it be
to use/integrate with rake?
Farrel
···
On 22/08/06, Kevin Clark <kevin.clark@gmail.com> wrote:
Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project. It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Finally, speak up if you're already using mkrf or have played with it.
I'm happy to hear criticism.
I hope this thread can give me a list of things to work on as I try to
move the project along.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Hi,
I tried it, but it doesn't work with my C++ extension. Though I can specify '*.cxx' with Mkrf::Generator.new, the resulting Rakefile has no rule for .cxx and so the rake command just says:
Don't know how to build task 'id3lib_api_wrap.o'
When I manually change '.c' to '.cxx' in the Rakefile, everything works alright.
Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project. It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Finally, speak up if you're already using mkrf or have played with it.
I'm happy to hear criticism.
I hope this thread can give me a list of things to work on as I try to
move the project along.
Were you able to add the features I described in my RubyForge forum post?
Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project.
Great.
It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
[snip]
I hope this thread can give me a list of things to work on as I try to
move the project along.
Well, you might make use of rubyforge to set up a mailing list. Then,
after some archives accrete and you have a better idea of what users
want/need, maybe get a tutorial together. That's what I'd like to see.
Also, a basic homepage (even if you just put the README up there)
would be nice.
I'm hoping to use mkrf in the next couple of weeks, but still need to
learn my way around a bit better.
---John
···
On 8/22/06, Kevin Clark <kevin.clark@gmail.com> wrote:
# Loads mkmf which is used to make makefiles for Ruby extensions
require 'mkmf'
# Give it a name
extension_name = 'digimarc'
# The destination
dir_config(extension_name)
# Get home directory (unfortunately not portable).
home = ENV["HOME"]
# Setup Digimarc Sdk path, add to includes and link. Assumes the sdk is
in
# a directory called "DigimarcSdk" directly in the user's home
directory but
# this can be overriden using the normal -with-digimarcSdk-include &
# -with-digimarcSdk-lib command line options.
digimarcSdkInclude, digimarcSdkLib = dir_config("digimarcSdk",
home+"/DigimarcSdk/Include", home+"/DigimarcSdk/lib")
# Non-portable way of linking our dynamic extension library with some
static library files
# from digimarc the sdk (".a" on linux). Uses full path since these
files are not affected
# by GCC/g++'s -L path settings.
# BTW: Not sure $LOCAL_LIBS is used correctly here but it works.
staticLibs = ["libBitmapIO", "libDWMEmb", "libDWMRdr", "libIWMPCom",
"libIWMRdr"]
staticLibExtension = ".a"
staticLibs.each { |x| $LOCAL_LIBS = $LOCAL_LIBS + " " + digimarcSdkLib
+ "/" + x + staticLibExtension}
# Non-portable way of specifying a C++ linker as required by Digimarc.
CONFIG['LDSHARED']="g++ -shared"
# Defines that os-specific flags that the digimarc SDK uses (also
non-portable)
$CFLAGS=$CFLAGS+" -D\"UNIX=1\""
Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project. It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Finally, speak up if you're already using mkrf or have played with it.
I'm happy to hear criticism.
I hope this thread can give me a list of things to work on as I try to
move the project along.
Hi guys,
Google's Summer of Code has officially come to a close but I in no way
plan to abandon my project. It's in a fairly stable place and working
for the libraries that I've played with. That being said, I don't
think many are using the project. mkmf is old, and though it is ugly,
I expect people are comfortable with it.
What can I do to help you make a switch? What feature does mkmf have
that you -need- for your extension? How can I make this easier?
Finally, speak up if you're already using mkrf or have played with it.
I'm happy to hear criticism.
I hope this thread can give me a list of things to work on as I try to
move the project along.
I would love to support it in my new build/task system to be release in
the next few days. I'm not a C coder myself, but if we could work
together on that, it would be great.
Hi Tim,
Thought it'd be hacky, you can add to vars using the new
.additional_code accessor (same with the header flags). I'm not really
satisfied with that either though, so I'm going to be investigating
implementing those features for the next release. You'll -definitely-
have a better way to access LDFLAGS and friends.
Kev
···
On 8/22/06, Timothy Hunter <TimHunter@nc.rr.com> wrote:
Kevin Clark wrote:
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project. It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> Finally, speak up if you're already using mkrf or have played with it.
> I'm happy to hear criticism.
>
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
>
Were you able to add the features I described in my RubyForge forum post?
Robin,
I'll look into that today and keep you updated.
Kev
···
On 8/22/06, Robin Stocker <robin@nibor.org> wrote:
Kevin Clark wrote:
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
Hi,
I tried it, but it doesn't work with my C++ extension. Though I can
specify '*.cxx' with Mkrf::Generator.new, the resulting Rakefile has no
rule for .cxx and so the rake command just says:
Don't know how to build task 'id3lib_api_wrap.o'
When I manually change '.c' to '.cxx' in the Rakefile, everything works
alright.
Farrel,
mkrf is for building Rakefiles to build extensions to Ruby. It uses
rake, but isn't a replacement for it. It aims to replace mkmf.
Kev
···
On 8/22/06, Farrel Lifson <farrel.lifson@gmail.com> wrote:
On 22/08/06, Kevin Clark <kevin.clark@gmail.com> wrote:
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project. It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> Finally, speak up if you're already using mkrf or have played with it.
> I'm happy to hear criticism.
>
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
>
> --
> Kevin Clark
> http://glu.ttono.us
>
Is it a replacement for a tool like rake? If not how easy would it be
to use/integrate with rake?
John,
I setup a mailing list at rubyforge just a moment ago. I'll send an
announcment to ruby-talk when it's up and ready to go.
I'll try to get a basic homepage up this week.
···
On 8/22/06, John Gabriele <jmg3000@gmail.com> wrote:
On 8/22/06, Kevin Clark <kevin.clark@gmail.com> wrote:
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project.
Great.
> It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> [snip]
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
Well, you might make use of rubyforge to set up a mailing list. Then,
after some archives accrete and you have a better idea of what users
want/need, maybe get a tutorial together. That's what I'd like to see.
Also, a basic homepage (even if you just put the README up there)
would be nice.
I'm hoping to use mkrf in the next couple of weeks, but still need to
learn my way around a bit better.
# Loads mkmf which is used to make makefiles for Ruby extensions
require 'mkmf'
# Give it a name
extension_name = 'digimarc'
# The destination
dir_config(extension_name)
# Get home directory (unfortunately not portable).
home = ENV["HOME"]
# Setup Digimarc Sdk path, add to includes and link. Assumes the sdk is
in
# a directory called "DigimarcSdk" directly in the user's home
directory but
# this can be overriden using the normal -with-digimarcSdk-include &
# -with-digimarcSdk-lib command line options.
digimarcSdkInclude, digimarcSdkLib = dir_config("digimarcSdk",
home+"/DigimarcSdk/Include", home+"/DigimarcSdk/lib")
# Non-portable way of linking our dynamic extension library with some
static library files
# from digimarc the sdk (".a" on linux). Uses full path since these
files are not affected
# by GCC/g++'s -L path settings.
# BTW: Not sure $LOCAL_LIBS is used correctly here but it works.
staticLibs = ["libBitmapIO", "libDWMEmb", "libDWMRdr", "libIWMPCom",
"libIWMRdr"]
staticLibExtension = ".a"
staticLibs.each { |x| $LOCAL_LIBS = $LOCAL_LIBS + " " + digimarcSdkLib
+ "/" + x + staticLibExtension}
# Non-portable way of specifying a C++ linker as required by Digimarc.
CONFIG['LDSHARED']="g++ -shared"
# Defines that os-specific flags that the digimarc SDK uses (also
non-portable)
$CFLAGS=$CFLAGS+" -D\"UNIX=1\""
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project. It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> Finally, speak up if you're already using mkrf or have played with it.
> I'm happy to hear criticism.
>
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
>
> --
> Kevin Clark
> http://glu.ttono.us
Trans,
Email me off list and we can figure it out.
Kev
···
On 8/22/06, Trans <transfire@gmail.com> wrote:
Kevin Clark wrote:
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project. It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> Finally, speak up if you're already using mkrf or have played with it.
> I'm happy to hear criticism.
>
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
I would love to support it in my new build/task system to be release in
the next few days. I'm not a C coder myself, but if we could work
together on that, it would be great.
At Wed, 23 Aug 2006 09:00:03 +0900,
mortench wrote in [ruby-talk:210014]:
# Non-portable way of linking our dynamic extension library with some
static library files
# from digimarc the sdk (".a" on linux). Uses full path since these
files are not affected
# by GCC/g++'s -L path settings.
# BTW: Not sure $LOCAL_LIBS is used correctly here but it works.
staticLibs = ["libBitmapIO", "libDWMEmb", "libDWMRdr", "libIWMPCom",
"libIWMRdr"]
staticLibExtension = ".a"
staticLibs.each { |x| $LOCAL_LIBS = $LOCAL_LIBS + " " + digimarcSdkLib
+ "/" + x + staticLibExtension}
Hi Tim,
Thought it'd be hacky, you can add to vars using the new
.additional_code accessor (same with the header flags). I'm not really
satisfied with that either though, so I'm going to be investigating
implementing those features for the next release. You'll -definitely-
have a better way to access LDFLAGS and friends.
Kev
Kevin Clark wrote:
> Hi guys,
> Google's Summer of Code has officially come to a close but I in no way
> plan to abandon my project. It's in a fairly stable place and working
> for the libraries that I've played with. That being said, I don't
> think many are using the project. mkmf is old, and though it is ugly,
> I expect people are comfortable with it.
>
> What can I do to help you make a switch? What feature does mkmf have
> that you -need- for your extension? How can I make this easier?
>
> Finally, speak up if you're already using mkrf or have played with it.
> I'm happy to hear criticism.
>
> I hope this thread can give me a list of things to work on as I try to
> move the project along.
>
Were you able to add the features I described in my RubyForge forum post?
