Seriously, though, I can’t imagine them being very different compared to Raspberry PI, provided you are using one of the Linux distributions on BeagleBone. Most likely it is just a matter of getting a different cross-compiler toolchain.

Alternatively properties that are not specific to a solution can be shared by loading the same Property Sheet in the various projects where required.

I suspect this would avoid the problems you encountered re VS2010 and VS2012 sharing

Not sure if const === serious.

Boost multi_index tries to protect one from accidentally changing the key by returning references to const elements from find(). There is nothing wrong with casting away that const qualifier, it is like saying: “yeah, I know the key must not change, I promise not to do that and I know what I am doing”.

int f() { return 42; }

int x = f(); // In this line, what we really want is a variable x of type whatever f() returns, which we have to write explicitly as int, violating DRY

auto y = f(); // This does not violate DRY, and matches the intention of having variable x of type whatever f() returns

That said, all these auto and decltype keywords make it more mandatory to have a good IDE with type induction. While previously you could use notepad and Search to find the type of a given variable, now that process becomes more convoluted. Instead, your IDE should be able to tell you what the type of any variable is right away.

template <typename T>
void g1 (T x);
 
template <typename T>
void g2 (T& x);
 
g1 (f ()); // T is int (not const int), x is int
g2 (f ()); // T is const int, x is const int&

const int& f3 ();
auto a3 = f3 (); // a1 is int

Then you say that

const int& f ();
auto& x = f (); // auto -> const int, x is const int&

Wouldn’t this imply that:
auto& x = f (); // auto -> int, x is int&

Yes, ODB wraps the SQLite transaction into the odb::transaction RAII class. While in the article I use the one transaction per log entry approach (see the body of the log() function), it is also easy to batch multiple log entries into a single transaction:

transaction t (db.begin ());
 
log (db, event (buy,  "INTC", 100, 25.10));
log (db, event (buy,  "AMD",  200, 4.05));
log (db, event (buy,  "ARM",  200, 26.25));
 
t.commit ();