Philip Nye wrote:
>
> Engineering Arts...
Well that didn't work well - here is the post I thought I'd sent:
Lennart Sorensen wrote:
On Wed, Jan 06, 2010 at 06:53:30PM +0000, g...@novadsp.com wrote:
Hello Martin
Re your first question if you are looking to use uCLinux then pick a
suitable processor. Unless the hardware budget is very, very, very tight
you will save endless amounts of time, energy, thus money using a
processor with suitable hardware resources. You'll get excellent and
free networking, driver stacks, tools, etc etc. There are very low cost
ARM7 solutions.
Certainly a good idea.
I would concur absolutely - a few bucks either way on the hardware cost is
neither here nor there on most projects when compared with the reduction in
development cost that can result from having more powerful hardware - the
only real reasons to aggressively shave the hardware budget are either that
your volumes are huge, or that you are a penniless hobbyist with no money
and plenty of time.
I'm a Windows developer who started using uCLinux a few months back...
For application development it was significantly faster to
edit/compile/debug vanilla ISO C++ using Visual Studio 2008(*)...
We just use gcc, makefiles, and avoid those awful IDE things that do
nothing but frustrate developers.
...
Well the problem is in looking for a good IDE. There is no such thing.
This illustrates the two extremes of development methodology and I won't
pick sides, but if you tend to the IDE extreme and have Windows experience,
then working from Windows with a Linux box (real of virtual) as a slave may
work well. If you prefer the makefile and command line method, then Windows
will probably cause frustration though it can be done. However, I have had
reasonable experience using Windows for editing whilst doing the rest by
command line on Linux. If you are planning to work with uClinux you will
need to get some grasp of command line and Linux operation anyway.
3. I wrote a combined TFTP server and serial-port console app that ran
on Windows which enabled me to download and run the 68K binaries.
This seems rather complex - the most common method is to have your build
system put its compiled binaries into a folder/directory which is
network-shared, then mount that directory as a network volume on the uClinux
target. The target then has huge file space available if it needs it, and
you can just run the binaries on the target with no visible download stage
at all since they are already within its file system. Works with either SMB
or NFS sharing.
Philip
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
