Dvsdk
From Attie's Wiki
(Difference between revisions)
m |
m (→Post-Install) |
||
| Line 12: | Line 12: | ||
==Post-Install== | ==Post-Install== | ||
The '''VERY''' first thing you should do is <code>make clean</code>. | The '''VERY''' first thing you should do is <code>make clean</code>. | ||
| − | Mainly because TI are stupid, and don't understand the concept of making a packaged release - the SDK will come with part-built | + | Mainly because TI are stupid, and don't understand the concept of making a packaged release - the SDK will come with part-built directories, some of which will make your build break with very weird errors. |
It's usually a good idea to keep hold of the installed SDK directory. Most of the files were downloaded (''not'' included in that ~1.5GB+ file you just 'executed'). | It's usually a good idea to keep hold of the installed SDK directory. Most of the files were downloaded (''not'' included in that ~1.5GB+ file you just 'executed'). | ||
Revision as of 15:32, 15 May 2012
Pre-Install
# put `uname 0022` somewhere in your persistent environment # kill off dash sudo dpkg-reconfigure dash # install fakeroot sudo apt-get install fakeroot
Post-Install
The VERY first thing you should do is make clean.
Mainly because TI are stupid, and don't understand the concept of making a packaged release - the SDK will come with part-built directories, some of which will make your build break with very weird errors.
It's usually a good idea to keep hold of the installed SDK directory. Most of the files were downloaded (not included in that ~1.5GB+ file you just 'executed').
Either make a tarball, use git, whatever
./setup.sh . linux-devkit/environment-setup make clean
Pre-Use
. linux-devkit/environment-setup
