On Sat, Jun 27, 2009 at 5:53 PM, Branko Čibej <brane_at_xbc.nu> wrote:
> Robert Dailey wrote:
> > Developers,
> > A few months ago I started a new open source GUI subversion client
> > named HareSVN and I'm now in the process of building Subversion on
> > Windows. My goal is to create a series of CMake scripts that will
> > build the Subversion library for the purposes of my personal project.
> > Hopefully the system will turn out well enough that it will be useful
> > to Subversion itself, but for right now it is only intended to be a
> > means to an end and will probably not be production-quality for the
> > first couple of passes.
> > Since I'm relatively new to Subversion's API, I am not 100% certain of
> > a few things. I do not know what preprocessor definitions must be
> > defined on Windows, nor how to modularize the code base (i.e. which
> > source files compile into what static libraries). I'm doubtful that
> > this is documented in any form, so I'm more than likely going to have
> > to either depend on the community for help or reverse engineer
> > makefiles to figure these things out. Of course, I prefer help from
> > the community (the developers) because this will be the easiest path
> > for me. However, if everyone is too busy then at the very least I ask
> > that someone point me in the right direction. Let me know which files
> > I need to look at to figure out all of the required details for
> > building under Windows.
> > I'm not familiar with the makefile language used on Linux, but I'm
> > hoping I can browse over the scripts and find the important information.
> > Any help anyone is willing to provide will be very helpful to me and I
> > will greatly appreciate it. Thank you.
> OK, lets put things in perspective. I really don't think we''d be
> interested in using a CMake-based build system. We have one of our own
> that has pretty much equivalent functionality, and while no-one is
> completely happy about it, I really suspect more people would be unhappy
> with CMake.
> If you were looking at SCons instead, that would be a lot more
> interesting; not least because APR-2.0 will most likely have a
> SCons-based build system.
I think you are misunderstanding me. With all do respect, I'm not doing this
as a contribution to Subversion. I'm doing this for my own benefit. If you
guys would not appreciate the work I'm doing, then by no means are you
obligated to accept it. As a side-note, I simply offered my work to the
Subversion team if they wanted it.
I'm simply asking for some help figuring out how to build Subversion. I have
a few simple questions that I would really appreciate answers to, and that's
pretty much all this thread amounts to.
The problem with the current build system for Subversion is that it isn't
portable. Many people have had a hard time building Subversion for Windows,
which is a primary concern of mine, and a big motivation for the work I'm
doing. Using CMake, I can generate visual studio projects that will build
Subversion and its dependencies on Windows, and I can generate Makefile
scripts for Linux, or even XCode projects for MAC. If those facts alone
still result in you being less happy about CMake than you would about the
current setup, then that's fine. You are entitled to that opinion. I'm not
here to argue about it either way.
Anyway, I'm still interested in knowing if libsvn_fs must be built for the
client. It seems as though it doesn't, and I plan to ignore it for now, but
it won't be until I begin to use the library that I'll notice things missing
due to linker errors. I hate to have to debug the issue like this, but if I
can't manage to get any help through the list I'll be forced to basically
"reverse engineer" the library to figure out what I need to do to make it
usable on the client side.
Received on 2009-06-28 01:05:47 CEST