tokafondo wrote:
I'm not qualified on anything!!!
The worst thing it would happen by trying is this
not working, and the best is me actually learning something, that could be worthwile of the effort or not.
Fair enough. There is no reason not to use makefiles to run a windows-only compiler under wine in Linux, if you so desire. Sure, why not! Worthwhile? Only you can tell, by actually trying your makefile and not asking others to do it for you.
tokafondo wrote:
I can't tell if running a compiler designed for another OS under emulation on linux could introduce bugs in the generated code. Many development has been done under emulation since the dawn of computers programming, so some reliability should be taken for granted.
I can guarantee 100% that it
could introduce bugs. Taking anything for granted, especially something as large as an emulation of a proprietary operating system is bound to bite you in the ass.
tokafondo wrote:
- Is it really useful to use autoconf, automake, configure and make themselves to manage 65xx code?
- Are bugs introduced by using a compiler under emulation, beacuse the compiler is not running under its native environment?
Yes, it is really useful to use tools that fit the job. If your makefile is so complicated that you can't take it anymore and you need a metalanguage in which you can specify your makefile, and have autoconf generate a makefile for you, it is the right tool. Whether the project contains 6502 code or not is irrelevant. And so on.
Yes, bugs are introduced under emulation. When running on real hardware, it is not uncommon to discover hardware issues. When developing in an emulator, it is likely that you will discover an emulator bug.
tokafondo wrote:
And again, this all started just by the curiosity of test if WDC's compiler is actually that bad or just an unknown gem.
I would not say that it is bad, and it is hardly unknown to us. Some of us avoid using windows because it is bad in oh so many different ways. Others don't like using tools without source code or a decent license. Many of us just don't care about C compilers.
Finally, when a makefile fails, it will not create garbage. Most likely it will be a silent failure, and you will spend the rest of the day trying to figure out why something that worked before stopped working. You will then slap your forehead, because you had an extra space in your makefile - it looked fine but failed to compile some file.
Make is a program that lets your build process to
selectively fail to compile certain files. When it works the way you wanted, by failing to compile files that didn't need to be compiled, you save milliseconds or seconds. When you accidentally fail to compile files, you are in for hours of trouble. It is a tool guaranteed to cause grief at some point in your life if you choose to use it. Choose wisely.