On 1/25/2013 5:35 PM, yoda wrote:
Hi DouglasAre you running John's version or have you got your own now?
Due to lack of hardware, I haven't been able to boot John's yet. There is some business about the IOBYTE that is
causing John's BIOS to ignore my IO board serial port, so when it boots, it bricks.
If I had a working system with plus, I would give consideration to just going with that. For me, it is about getting
a usable build scenario so I have a known good starting point to move on from.
Please what is the hardware configuration required to run what you have?
I really want to work in conjunction with you and not waste engineering time duplicating effort or moving backwards
instead of forwards.
I am also interested in making my utilities portable across the operating system boundaries (with a re-compile).
I have been writing them in C since RomWBW 2.0. I would like to dialogue with you about this topic.
The situation with the Makefile's is that my attempt at writing one Makefile for all three platforms was rejected
as being overly complex, although it was only complex enough to do the job in my opinion. I really don't like
the Windowsisms at all and would be happy to see them gone. Unfortunately, Wayne (God bless him, and no
harm, to him intended, he is my pal) is totally involved with the Microsoft way at work, and unfortunately his
choice of development platform is Windows, and he would rather write CMD scripts then use the industry
standard "make". I have crafted three Makefile's for RomWBW, and they work like this.
The three build folders for my makes are XSource, LSource, and WSource. All these folders contain in the
distribution is a Makefile and a bin folder with platform specific tools. You enter the proper folder for your
platform and say "make clean" and "make". it takes approximately 10 seconds on Windows, and about 1.2
on Linux, and about 2 on Mac OS X. The makefile coppies in needed source files form ../Source and converts
the end of line as appropriate for the platform tools. The all generated files end up in the *Source folder and
none show up in the Source folder, thereby leaving the Source folder pristine. Wayne continues to use his
build.cmd and .ps1 files for the Windows build, and I am constantly having to update the makefiles every time
he breaks things. I am ready to go back to one Makefile for all three platforms but I have core issue
disagreements with Dave Giles about how platform tools are handled. He wants each and every tool individually
installed by the builder on his system, then for the builds to find them in /usr/local/bin instead if in a local
bin folder in the distribution. Linux seems to be the issue, Mac OS X binaries seem portable, but there are so
many Linux distribs that it is hard to ship embedded linux platform tools and hope they are compatible with
whatever religiously affiliated Linux distrib a builder had attached to. I use Scientific Linux, which is in essence
Red Hat Enterprise Server.
I want to work things out with you and move forward optimally. Lets keep that dialogue alive. The things you
are saying to me make sense and I trust your perspective.