> > . . .and the chances you'll need a cross compiler toolchain, and IDE are > near nil. >
For your own code. Unless you're one of *those* (them?!) code zombies who eat's sleeps and breathes caffine. Writing 5M lines of bug ridden code a day ;) On Fri, Sep 30, 2016 at 6:37 PM, William Hermans <[email protected]> wrote: > mz, > > While the subject has been brought up. If you've had any experience with > Linux development in the past. This experience would largely be the same. > You do not need a cross compiler or 99.9% of what all is out there, and the > chances you'll need a cross compiler toolchain, and IDE are near nil. > > For instance, my own setup is a bit "complex" in setup, but makes my own > daily development very simple. I started off with a seperate Debian system > running Samba, and an NFS share specifically for the beaglebone. Like so: > > william@beaglebone:~/dev$ df -h . > Filesystem Size Used Avail Use% Mounted on > 192.168.254.162:/home/william/share 136G 51G 79G 40% > /home/william/dev > > I then use Samba to share this same directory out to my main Windows > development system. Where I simply edit code in either Sublime text, or > Visual Studio Code. Any text editor that works for you will be fine. But > the point of this whole setup is that I have a central place to store all > my source, where my Windows development system can access those files as if > they were local files( because of Samba, and Windows " Map Network Drive"). > > Once finished, it's a simple matter of: > > $ gcc -Wall source_file.c -o target_binary_name > > Depending on how complex your source is, it may be better to use > makefiles, but that's a subject I try to avoid myself . . . there are all > kinds of build tools in this area. > > Honestly, in three and a half years. Short of tinkering with compiling my > own kernel. I've never had to cross compile anything. The above setup > though is how one would avoid writing( through compile from source ) to the > eMMC, or an sdcard. Which will help keep from prematurely destroying > either. Another way, for small projects would be to setup a tmpfs ramdisk, > 64M, or even 256M( yes I've personally used 256M occasionally ). You would > just need to make sure to copy your changes, if needed to someplace safe. > cp /path/* target, mv /path /target, or even setup a cron job to rsync the > files to another location every few minutes . . . Again, the only limit > here is your imagination. > > On Fri, Sep 30, 2016 at 5:41 PM, William Hermans <[email protected]> > wrote: > >> Well, there seems to be a lot of confusion between toolchains, which no >> one really asked or said anything about( I made a passing remark ), Linux >> kernel, and Linux image. My own idea of what makes a Linux image is a >> complete "package" that contains bootloader(s), a Linux kernel, and a >> rootfs(root file system ), and assorted other files. In other words, >> anything / everything needed to run a complete boot-able image. >> >> As far as compiling C from source. I do not recall the OP asking or that >> information. >> >> On Fri, Sep 30, 2016 at 1:42 PM, mzimmers <[email protected]> wrote: >> >>> Thank you, Graham. I just ordered a starter kit and Mr. Molloy's book >>> from Amazon. Come next Monday I'll have something to tinker with. >>> >>> I appreciate everyone's input. >>> >>> mz >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/beagleboard/b79ae34c-8f78-442e-a5bf-817b790de0c6%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/b79ae34c-8f78-442e-a5bf-817b790de0c6%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrOo6hvyU07jswfVLXzWsz2iSEnaq7ZEKir46pftgCKDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
