search

rdmenezes / wvstreams

Automatically exported from code.google.com/p/wvstreams
0 stars 0 forks source link

Building from Subversion #3

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
From a fresh checkout, it's not quite obvious how to build WvStreams and
friends, and there are also bugs (for example, WvDial expects TOPDIR to
build in-tree, and a wvrules.mk at the top which doesn't exist).

The process should be reviewed, bugs filed, and then documented
(preferably, this could be optional, or brief to the point of "run 'make'
and follow the instructions").

Original issue reported on code.google.com by pphaneuf on 7 Mar 2007 at 10:19

GoogleCodeExporter commented 9 years ago 
One of the issues I was having was constant relinking. I isolated it to a broken
symlink for a number of things in the wvstreams directory, and the usage of 
"-lfoo"
as dependencies in some makefiles. It's probably what we want, actually, but it 
seems
to fail silently when it's missing, just counting as having been redone, and 
so, it
relinks every time.

Fixing the symlinks make it actually get a grip on something to compare the 
timestamp
of, and it stops relinking all the time.

As a side-note, the bare minimum option for wvstreams seems to be 
LD_LIBRARY_PATH
pointing at wherever we put all the libraries.

Original comment by pphaneuf on 7 Mar 2007 at 3:05

GoogleCodeExporter commented 9 years ago 
In addition to the problems you mention, it's also pretty much impossible to 
run unit
tests for new subversion modules right now (e.g.: wvtftp's unit tests just flat 
out
don't work).

I think our choices are either to refactor wvrules.mk to be more appropriate 
for our
current development model or to switch all out to a new build system. I'd 
probably
favor the latter, so long as it doesn't suck (this means automake is pretty 
much out
of the question). 

I'm currently investigating cmake for another wvstreams-based project I'm 
working on.
It's used in many popular projects (kde, chicken) and seems to be pretty sane. 
I'll
let everyone know what I find.

Original comment by wrl...@gmail.com on 7 Mar 2007 at 6:08

GoogleCodeExporter commented 9 years ago 
I have been working on and off on a simple build system that relies on autoconf 
and
GNU make (as opposed to automake, which avoids relying on GNU make), makes it 
easy to
do non-recursive makefiles and provides a number of the GNU standard targets 
(such as
"check"), as well as supporting out-of-tree building (useful for 
cross-compiling,
which I do all the time in a Debian "etch" chroot on my Ubuntu 7.04 system).

http://pphaneuf.googlecode.com/svn/trunk/makefiles/

Original comment by pphaneuf on 30 Sep 2007 at 6:36