10 Nov 2000 mvw   » (Journeyer)


Got a nice hint about sources across directories from Gary Vaughan:

> I keep my main sources in
>     project/src
> have tests in
>     project/test/test01
> I don't manage to compile a small test program in
> the above test01 directory, that uses a source file
> from project/src.
> What should I do?
> - create the test binary in project/src rather than
>   project/test/test01?
> - build some library just for the purpose of testing
>   that I won't use anyway?
> - use some secret potion from CVS automake?

The 2nd option would be best, automake doesn't handle sources outside of $srcdir or $builddir (except for header files of course). You might try setting SUBDIRS in the project dir to descend src before test, and then linking test01 with (from memory, so check the docs):

test01_LDFLAGS = -static test01_DEPENDENCIES = $(top_builddir)/src/foo.o test01_LDADD = $(test01_DEPENDENCIES) or suchlike to link the compilation object in directly.


Today I dropped back to Observer status. I should read the trust metrics explanation to understand this. It can't be related to the number of certificates I have, as there are other persons who have less. So it must be related either to the fact that I certified a lot of people or to the relative positions of the people who certified me. Interesting.

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!