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

okay, i spoke before experimenting. confirm what i observe: the fix-embedded-paths tool will traverse a directory search path (the 3rd argument) and replace all occurrences of the <old root> with <new root>. is this correct?

one other question: why is there a limitation that the <new root> must be shorter or the same length as <old root>?



At 02:55 PM 5/19/2005, Royce Kemp wrote:
Usage: ./fix-embedded-paths <old root> <new root> <directoryToSearch>

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

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?

./fix-embedded-path /opt/crosstool/$TARGET/$TOOLCOMBO /$HOME/myproj/toolchain ???

thx. 



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

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