On 12/22/2013 11:59 AM, Al Kossow wrote:
On 12/22/13 9:34 AM, Al Kossow wrote:
I think I've tried doing this for several
years running now
and gave up when after buying a prototyping board I couldn't get
anything
to work
My problem is I get really frustrated when something doesn't just WORK.
You download something to what you would think is supported (a modern
Linux or OS X) ./configure, ./make and it pukes. I went through this last
night with trying to build arm-none-eabi et. al. from macports. Now, I'll
try to find the right pieces for Linux instead, since I set up a core
2 duo
running Ubuntu to run Quartus on.
To be honest, though, a lot of things DID just work when installed,
not that
I'm particularly happy with HOW they work (I was looking at both
Eclipse and
CodeBlocks IDEs). I think I understand now why Eric Smith just uses
the bare
tool chains.
I know people will flame me for this, but I do initial dev on a Windows
box for this reason.
Prepackaged bins are usually available for Windows, so no builds needed.
Then, once I have success, I build on my Linux box.
I also try to use the same toolchain on both. Eclipse for all projects,
GCC, etc.
Jim
--
Jim Brain
brain at
jbrain.com
www.jbrain.com