relative source file path vs. subversion branching

[Holger Birkmeyer (ng4T)]

Dear all,

I cannot figure out, what the best way is to get rid of relative paths
in my Makefile.am

Within our svn project structure we have multiple projects (A, B, C...)
using common files from a COMM_include project. Those files are
referenced with a relative path in Makefile.am (see below)

libcommmapmsc_la_SOURCES = \
    hlr_ussdmenu.cpp      \
    ../../../COMM_include/trunk/functions/smscode.cpp

Now, when the location of project A changes due to subversion branching,
the relative paths are not correct anymore.

I have tried to replace the relative paths with a global variable $(TOP)
I have set in configure.ac with the help of AC_SUBST and pwd and sed.
However, that led to numerous other problems in the context of
dependency tracking. One of those was, that configure did create the
.Plo files in a directory called "src/$(TOP)/COMM_include/...." without
substituting $(TOP). This would create the .Plo files in the wrong place
leading to a failure of the Make process later.

To make a long story short: My question is: Is my approach to reference
common files with relative paths the wrong approach?

Regards,
Holger

-- 
Holger Birkmeyer
Engineering
fon: +49-30-652185-95
fax: +49-30-652185-31

ng4T GmbH
Siemensdamm 50
13629 Berlin
Germany
www.ng4t.com

Berlin-Charlottenburg, HRB 123546
Geschäftsführer Dr. Andreas Kallmann

signature.asc
Description: OpenPGP digital signature