John, it's not necessarily impossible, but you should really understand what you're doing. Also, I'm still learning some myself, and what I mean by this is that you do not have to understand 100% of it all to achieve certain goals. For your case here however, I think you need to understand how the compiler, linker work together, and how to setup the toolchain to use the correct libraries / shared object files.
So getting a good book on GCC ( as in the toolchain ), then reading it will give you a very good start on that. Not only this, but knowing this information will help you with using *any* gcc toolchain. Not just for this specific case. These listed below may help you understand enough: ftp://gcc.gnu.org/pub/gcc/summit/2003/Building%20and%20Using%20a%20Cross%20Development%20Tool%20Chain.pdf http://simplemachines.it/doc/toolchHOWTO.pdf Also, sometimes ( very often ) you can google your exact error message that gcc spits out and at least glean enough information on how to fix your problem. Of course understanding you toolchain, and having hand on experience with how to google various kinds of errors helps. Sometimes, you can just paste part of the error message and find an exact explanation to a fix. This however does not mean finding the very last error on the command line output will help. This means, you need to go back up as far as you can to find the first inkling of an error. There used to be a few good GNU gcc toolchain books online for free I thought, so if i happen to run across these again, I'll shoot you a link in here. On Mon, Aug 11, 2014 at 12:37 PM, Robert Nelson <[email protected]> wrote: > On Mon, Aug 11, 2014 at 2:36 PM, John Geddes <[email protected]> wrote: > > > > > > On Monday, August 11, 2014 7:05:32 PM UTC+1, William Hermans wrote: > >> > >> Unfortunately, there seems to be no exact steps guide how to achieve > this, > >> and I honestly do not have the time to teach anyone "step-by-step" cross > >> compiling. So, I recommend that you pick up a book on gcc toolchains, > and > >> start reading. It will take time to absorb this information, but it is > >> something everyone must do to fully understand what they're doing. > >> > >> Once you do understand things more clearly, then perhaps you'll be able > to > >> google and read about cross compiler setups, and pick out bits, and > pieces > >> of information that will apply for your own situation. > > > > > > I was beginning to come to the conclusion that the idea of a non-Linux > > person "dipping in" to learn just enough to do the basics for C++ on BBB > is > > impossible.You have confirmed this - I appreciate your advice. > > > > There is great temptation to try and dip in - Derek Molloy's BBB/C++ > video > > seems to offer nice simple steps to do the basics, but then you hit > > something that you need that he doesn't cover (CURL for example) and > > immediately you are in very scary territory. Back to Arduino, (or at > best, > > bonescript), I fear. > > Why can't you build it on the BBB? > > "cross-compiling" is just a self imposed headache no one really has to > deal with.. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > > -- > 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]. > 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]. For more options, visit https://groups.google.com/d/optout.
