Rockbox Development > Starting Development and Compiling

Will rockboxdev.sh upset my system?

(1/2) > >>

bascule:
I've done a forum search for this, but despite some tantalising snippets of information, I can't find a direct answer to this:

I run PCLinuxOS on my machine, and the devs are very insistent about not installing packages from outside their repo.

Obviously, I'm wanting to run rockboxdev.sh, but I get the impression from the Wiki and these forums that it will overwrite my system's gcc version with it's own one and update the PATH to include things that may cause errors with the system operation.

Is this true, or have I misunderstood what it does?

gevaerts:
That's wrong. rockboxdev.sh installs by default in /usr/local/arm-elf/ (or m68-elf,...), and tells you what to add to the PATH. It doesn't change the PATH itself, and you can override the install location

LambdaCalculus:

--- Quote from: gevaerts on July 01, 2009, 08:18:51 AM ---and you can override the install location

--- End quote ---

This feature was especially useful when I wanted to set up a Rockbox build environment in OpenSolaris; I had to install to /opt/local instead of /usr/local there (OpenSolaris doesn't allow outside apps to install to /usr/local).

AlexP:
rockboxdev.sh uses your system gcc (which compiles code for your CPU architecture) to compile versions of gcc (and binutils) for the CPU architecture in the targets (e.g. arm, m68k, ...).  It doesn't touch your system ones.

GodEater:

--- Quote from: LambdaCalculus379 link=topic=22091.msg152536#msg152536 ---This feature was especially useful when I wanted to set up a Rockbox build environment in OpenSolaris; I had to install to /opt/local instead of /usr/local there (OpenSolaris doesn't allow outside apps to install to /usr/local).

--- End quote ---

Because allowing you to install outside apps in /usr/local (which is the WHOLE POINT OF /usr/local) is just dumb if you're a solaris engineer.

Navigation

[0] Message Index

[#] Next page