Until git is added to the BSP, here's a (reasonably) straightforward way of getting git onto your Edison:
If you want to build a git package that you can in install yourself onto your Edison, here's an outline of how you'd go about it. I'm using a Linux box as my build machine for this.
- Get the Edison SKD and the "Edison Linux Source Files" from here: Edison - Software Downloads
- Install those as per the documentation.
- Then, to make a git package do 'bitbake git'. This will create git_1.9.0-r0_core2-32.ipk in .../edison-src/build/tmp/deploy/ipk/core2-32
- Copy git_1.9.0-r0_core2-32.ipk on to your Edison board
- Run 'opkg install git_1.9.0-r0_core2-32.ipk'.
Now you should have git available on your Edison.
1 of 1 people found this helpful
The IoT Devkit has a yocto repo up here
I have had great success installing 'missing' packages (git,bison,flex,alsa-utils, etc) from this repo (everything seems to work ok). All you have to do is add the following /etc/opkg/base-feeds.conf
opkg install git
I second the need for git. Among other things, the lack of git also breaks many Node.js package installations (i.e. I wanted to install the npm package node-core-audio to use USB audio from Node, but "npm install node-core-audio" fails because git is not present). I can install node packages using the XDK... but I STILL want git for other things on the command line, including npm.
BTW, some command-line tools for USB audio would be useful; "aplay", for instance. I also don't see uvc and uvctools (and things like "uvccapture" would be very useful for the same reason as aplay: to write scripts that can talk to USB devices, which after all, is one of the differentiators of Edison compared to MCU).
For git and other dev packages, it would be ok IMO if there was an extra step like "opkg install git". Adding the above repos works... but references to these repos should be in the standard image, I think. I *don't* want to have to fork off my own image.
Installing git (1.9.0-r0) to root...
* copy_file_chunk: write: No space left on device.
* opkg_conf_write_status_files: Couldn't close //var/lib/opkg/status: No space left on device.
Filesystem Size Used Available Use% Mounted on
/dev/root 463.9M 453.5M 0 100% /
systemd-1 2.2G 303.1M 1.9G 13% /home
/dev/mmcblk0p10 2.2G 303.1M 1.9G 13% /home
who thought this was a good idea?
I ended up moving /usr/lib/node_modules to /home/node_modules, since I was installing a bunch of modules:
tar cpf - * | (cd /home/node_modules; tar xpf -)
rm -r node_modules
ln -s /home/node_modules
After doing this, I had plenty of room for opkg packages.