This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: fix-embedded-path

From: Daniel Kegel <dank at kegel dot com>
To: Royce Kemp <rkemp at ip3 dot com>
Cc: crossgcc at sources dot redhat dot com
Date: Thu, 19 May 2005 14:59:55 -0700
Subject: Re: fix-embedded-path
References: <6.0.1.1.2.20050519145002.01e388c8@insight.ip3.com>

Royce Kemp wrote:

Usage: ./fix-embedded-paths <old root> <new root> <directoryToSearch>

what's the <directoryToSearch>? Can someone elaborate on how this works?


That's where the files to modify are.  (Sorry if it was named poorly.)
It was done this way so you could do the fixup either before or
after copying.

I'm interested in copying a toolchain, say from /opt/crosstool/$TARGET/$TOOLCOMBO to /$HOME/myproj/toolchain. Will fix-embedded-path help me do that?

Yes.

cp -r /opt/crosstool/$TARGET/$TOOLCOMBO $HOME/myproj/toolchain
fix-embedded-path  /opt/crosstool/$TARGET/$TOOLCOMBO $HOME/myproj/toolchain $HOME/myproj/toolchain

(But you should consider generating the toolchain in
the final location in the first place; fix-embedded-paths
works for me, but it's a hack, and one person has reported
a problem with it.)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- fix-embedded-path
  - From: Royce Kemp

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]