On Thu, 28 Oct 2004, Yann COHEN wrote:
> Hello,
>
> I just install subversion over a debian server.
> All it's fine.
>
> Question
> we develop a projet with to hardware targets (two kind of CPU and
> development tools) but we need to share some files (e.g. header of
> communication protocol).
> A least one of them can be only a read only version.
>
> After A very fast read of the documentation, I don't find any way to do
> this.
>
> So how can I do for carry out this sharing ?
I was doing just that last week. We did the same thing the other
listmember suggested, we have ARCH_ARM and ARCH_x86 directories below the
one holding the architecture-independent code, and the makefile sucks in
the right ARCH_* based on the definition of $(ARCH). The nice thing about
doing it this way is you can set ARCH as an environment variable, or as a
parameter to make, or derive it from something else inside the makefile.
If you think about it, you really do want them in the same project. After
you get them both working, and most of the changes are API changes and
added functionality, you're usually going to have to change both
architectures.
together.
----------------------------------------------------------------------------
DDDD David Kramer david_at_thekramers.net http://thekramers.net
DK KD
DKK D Python is executable pseudocode
DK KD Perl is executable line noise
DDDD Bruce Eckel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 29 18:55:50 2004