-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 28 January 2002 22:15, Yoshiki Hayashi wrote:
...
> extonf.rb more. It would be great if you could address
> those and make extconf.rb more generalized. Then it could
> be added to the repository.
Sure.
> The main reason is that I haven't had time to improve my
> extconf.rb. Another reason is that since Subversion has
Ah, yes. Somebody had mentioned that you had one, somewhere, but were
withholding it until some threading issues were resolved.
> only one central Makefile, I wanted to compile Ruby binding
> from that Makefile. However, it would be nice for some user
...
Greg Stein later said:
> I'd say go ahead and add it. When this stuff all stabilizes, then we'll
> integrate the Ruby bindings into the top-level Makefile. The JNI bindings
> all all the various SWIG bindings have the same issues.
I agree with Greg. I don't know how this will mesh into the final build
system; this is a similar issue as has been mentioned about the possibility
of using Ant for the Java binding, with a critical difference: extconf knows
about the Ruby installation. In fact, it is an expert about the Ruby
installation, and it would be prudent to use it, if permissable.
> without reconfiguring whole Subversion again, so I'm not
> against adding extconf.rb to the repository.
Hooray!
> Actually, svn.so is the name of the library. Other Ruby
> DSOs are named similar way like zlib.so and digest.so.
Ok.
> Perhaps it needs dir_config(svn) so that one can specify
> --with-svn-dir=/opt/svn or something.
Ok.
> There are libsvn_fs and libsvn_repos missing. And apr stuff
> should come from apr-config --libs. Also, CFLAGS should
> come from apr-config --cflags instead of hardcoding -pthread and -O.
The library compiled without complaint sans those libraries; doesn't linking
against libsvn_fs limit the Ruby binding to server installations?
Greg Stein later said:
> At some point, we'll want to make portions of the bindings dependent upon
> whether the FS was built or not.
I've done this. The extconf.rb now links against libsvn_fs and libsvn_repos
if they exist, otherwise, it doesn't.
I've attached the revised extconf.rb; I've made the rest of the changes you
suggested. I also took out the second code block that added special flags
based on the platform, since that's apr's domain.
Also, because of how I installed apr, my new extconf.rb with apr-config
doesn't work as flawlessly as before. I have apr-config installed in
/usr/local/bin, which isn't in root's PATH. This isn't really a problem; I
just add the path, but I don't know how common a system like mine is, and I
wonder if there should be a README or something about this. Also, the new
make generates beaucoup warnings, because of the changed cflags. Just an
FYI.
Question: apr-config --libs doesn't include libapr or libpthreads; yet
apr-config --cflags specifies --pthread. I'm not an apr-config expert, but
this seems ... wrong. In any case, I left the pthread library in the list of
dependencies.
Last question: were you planning on documenting the API, or should I give
that a shot?
- - --
|.. "I shall move among them, like an invisible... ... ... thing."
<|> -- Ace, "Ace Ventura, "Pet Detective II"
/|\
/|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8VumRP0KxygnleI8RAkjJAJoDjrnV44kKfpTaDzn9i7DmzlLY6QCfebzE
xa8aKjV8xg4t9WVXDjSJvlE=
=ArRP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:01 2006