And On This Farm He Had A Blog

03:22. If I leave for the office now, I can get this environment build duplicated on my main dev machine before people come in and bug me. By the time I get on the phone with a supplier in Atlanta to ask, "I noticed that the things I ordered are not yet in transit. Why is that?" and deal with the avalanche of typical Monday calls, the various builds will be chugging right along.

Mulling over going to a web-based way to hit the git repository rather than the ssh one I am presently using.

Monday, I am in you.

AND I AM NOT LIKING IT ONE BIT.

@c Consider yourself pelted with tomatoes for saying that.

Once the major stuff is fully "Wintel'd" and has shipped, I will hand it off to someone else and do the Linux stuff myself.

Hopefully, the end result is going to be a streamlined build, test and bug reporting environment that won't make people I bring into the project go all "Deer in headlights" on me.

All of this work to eliminate building platforms might strike some as silly but keep in mind I have been juggling three versions of Visual Studio, Metrowerks CodeWarrior, and a massive Linux/Autotools monstrosity for years.

It just makes sense to me to eliminate the energy expended on that mess and apply it where it belongs - The damned code.

@matigo Had to move it back over to Metrowerks eventually because juggling the sheer number of code segments in that project became a juggling chainsaws thing. Also had to resort to assembly in a few spots. Was just easier to do that under Metrowerks.

@matigo The only real headache I had was during the period I moved everything over to Linux for the build using an ugly cross platform fork of gcc known as prc-tools. There was no Linux binary of the scanner library. A Symbol engineer was nice enough to rectify that for me. It was an amazing community while it lasted.

Since I am eliminating Linux from the equation for the forseeable future, this gives me a chance to try WIX for installer generation.

Our old Windows installer was actually built under the Linux build tree with NSIS under wine. Had the NSI file files generated directly from configure. Don't judge. It made perfect sense at the time

@matigo Symbol SPT-1500/SPT-1800 bar code scanning units and Visor Handsprings with CSM-150 scanner modules.

My earlier build headaches with QT had a simpler solution..grumble…grabbed the 5.7 build directly from git. Much smoother.