This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
relative path options
- From: Helen Snitkovsky <helens at hydrix dot com>
- To: ecos discuss group <ecos-discuss at ecos dot sourceware dot org>
- Date: 05 May 2004 12:41:13 +1000
- Subject: [ECOS] relative path options
- Organization:
Hello,
I tried to arrange ecos environment for developers as follows:
1.build eCos for Synthetic target from configtool template (default
syn target) at $ECOS/work directory, where $ECOS is defined shell
variable and ecos sources resides at $ECOS/ecos-2.0b1
2. Check it in to CVS.
3. Then a developer creates its own directory $eslewhere, creates,
compiles and debugs sources in there with reference to eCos library he
had checked out from CVS. Of course, his CVS working directory is
different from mine
4. Anyway, when I tried to follow all that way, we failed to debug
twothreads program built by means of provided Makefile. The dbg is still
looking for main.cxx from my CVS working directory, which is stored
locally on my machine. Moreover, somehow the object file that was
produced by that Makefile contained paths from my repository.
Using gcc -static flag did not solve the problem.
Is there any way to solve this problem?
Thanks in advance,
--
Helen Snitkovsky
Software Engineer
Ph: +61 3 9509 3724
helen.snitkovsky@hydrix.com
Hydrix Pty Ltd.
1356 High St,
Malvern, 3144,
Victoria,
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss