This illustrates the two extremes of development methodology and I won't
pick sides, ... If you are planning to work with uClinux you will
need to get some grasp of command line and Linux operation anyway.
To clarify, the approach I outlined uses the standard Win32 ports of the
GCC tool chain. It is simply that makefile(s) are derived directly from
VS projects and not created using autoconf & friends or edited by hand. (*)
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.
A valid comment but there is an additional dimension. Recall this was a
mixed Windows/Linux project. The guys at the coal face (almost
literally) did not have sufficient resources/control/expertise to
install, configure and lock down SMB/NFS. A simple Windows based console
with a serial connection did the trick.
Jerry.
_______________________________________________
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
