Jonathan Marsden wrote:
Greg Hellings wrote:
Because there are some people who have no desire to learn anything
about autotools ...
Which is fine. That is their choice. Such people by definition should
probably not also choose to be volunteer developers on a project that
uses autotools.
Am 12.05.2009 um 04:47 schrieb Greg Hellings:
Additionally, MSYS and (I believe) Cygwin are horrible environments
to try
to use... (I haven't used Cygwin, but I have used MSYS)
For one thing, ICU's native build environment for Windows is MSVC -- I
believe Matthew has built it, finally,
Eeli Kaikkonen wrote:
If some aspect of a project has a problem, it should be fixed.
Agreed. Other than not supporting some proprietary OSes as well as some
might wish, is Autotools as a build system really a significant problem
for SWORD? It seems to be building it OK for me (and I have
I don't see what all the fuss is about. I know nothing about autotools
or configure other than SWORD uses it and that it is common.
What I do know, it is simple to build the SWORD library.
1) Check out the files:
svn co http://www.crosswire.org/svn/sword/trunk sword
2) Enter the build
I know someone's going to jump on me about this being in the
documentation already, but the process below is not always so easy for
folks like me, and the process DM outlines is not all in one place in
the documentation. This should be in sword/INSTALL under QUICKSTART and
on the website
On Tue, May 12, 2009 at 1:13 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
Greg Hellings wrote:
To test the building process of BibleTime, which I do work with, I
often build against sword-svn. Having the autogen.sh keeps me from
having to remember what autotools options are needed, etc.
I just updated to the latest SWORD svn and ran autogen.sh and
usrinst.sh. Forgetting that I was in a fresh install of Ubuntu, I
didn't think to manually install g++, so I have no C++ compiler on my
system. Nevertheless, the configure script simply noted this and
moved on, completing the
Greg Hellings wrote:
I just updated to the latest SWORD svn and ran autogen.sh and
usrinst.sh. Forgetting that I was in a fresh install of Ubuntu, I
didn't think to manually install g++, so I have no C++ compiler on my
system. Nevertheless, the configure script simply noted this and
moved on,
On Mon, May 11, 2009 at 1:37 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
Greg Hellings wrote:
I just updated to the latest SWORD svn and ran autogen.sh and
usrinst.sh. Forgetting that I was in a fresh install of Ubuntu, I
didn't think to manually install g++, so I have no C++ compiler
Greg Hellings wrote:
The install was not 100% fresh... I had already tried to do
autotools.sh, and thus installed automake/conf and libtool.
OK. I suspect that the number of developer machines out there which
have a working autotools installation, but no C++ compiler, is fairly
small :)
autogen.sh is (typically) a part of gnome, and is commonly used in
gnome development, including xiphos. The autogen.sh in sword appears
to more or less copy the functionality of gnome-autogen.sh. It is not
needed with release packages, only for doing svn development.
Matthew
On Mon, May 11, 2009 at 4:00 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
Greg Hellings wrote:
The install was not 100% fresh... I had already tried to do
autotools.sh, and thus installed automake/conf and libtool.
OK. I suspect that the number of developer machines out there which have
Matthew Talbert wrote:
autogen.sh is (typically) a part of gnome, and is commonly used in
gnome development, including xiphos. The autogen.sh in sword appears
to more or less copy the functionality of gnome-autogen.sh. It is not
needed with release packages, only for doing svn development.
On Mon, May 11, 2009 at 7:13 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
Matthew Talbert wrote:
autogen.sh is (typically) a part of gnome, and is commonly used in
gnome development, including xiphos. The autogen.sh in sword appears
to more or less copy the functionality of
Greg Hellings wrote:
Because there are some people who have no desire to learn anything
about autotools ...
Which is fine. That is their choice. Such people by definition should
probably not also choose to be volunteer developers on a project that
uses autotools. The project team chose
On Mon, May 11, 2009 at 8:57 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
Greg Hellings wrote:
Because there are some people who have no desire to learn anything
about autotools ...
Which is fine. That is their choice. Such people by definition should
probably not also choose to be
Greg Hellings wrote:
To test the building process of BibleTime, which I do work with, I
often build against sword-svn. Having the autogen.sh keeps me from
having to remember what autotools options are needed, etc.
Which is exactly what autoreconf does, and why it exists :) And
learning to
On Tue, May 12, 2009 at 1:13 PM, Jonathan Marsden jmars...@fastmail.fmwrote:
Probably. Proprietary development environments like this are just not
often seen as critical targets for open source tools, I would think.
Especially when it's not really clear what the benefits of MSVC and
OK. Then we can hide the autoreconf command by a one line shell script
called autogen.sh, that just runs autoreconf, if that is really less of
a burden to new developers. It seems like roughly the same amount of
memory needed in either case, to me, and memorizing autoreconf is useful
across
On Mon, May 11, 2009 at 10:23 PM, Ben Morgan benpmor...@gmail.com wrote:
On Tue, May 12, 2009 at 1:13 PM, Jonathan Marsden jmars...@fastmail.fm
wrote:
Probably. Proprietary development environments like this are just not
often seen as critical targets for open source tools, I would think.
20 matches
Mail list logo
