Hi... Yes, I have Cygwin too, not on this PC though. I got it for the sshd facility a couple of years ago, a very good robust fallback VPN whenever I need it. Mind you, installing that was not painless either, needing several downloads and builds to get all the bits needed working correctly. I dred to think if I ever need to re-install it, the original website with the instrucitons on, has long gone, and quite where my notes about it all are, goodness knows.
The only "package" I have successfully installed on the Linux machine, was funnily enough Sun's Java RTE, as what came with the linux distribution didn't work very well, if at all. Sun's instructions were on the nail, and it went on first go, and then worked "out of the box" as it were. I tried a few other things, but there are "holes" in the instructions, and no help forthcoming from the "experts" either. It's been a while since I built anything (software wise that is) for PIC's, then using a much earlier MPLAB, and working in assembler. Not painless, but so many fewer ways to screw up (in the IDE anyway) I used to have the HiTech PICC Lite package, that worked realy well, but it didn't take kindly to being installed on XP, so I have left that on an old W98 machine, for any needed changes to that project. What I'm learning at the moment, is it seems that there is no such thing as *Standard* C code any more. OK, the basic C stuff is still much the same, and much of it ANSI compatible, notwithstanding C++ (or C#) of course. (I've spent some years working with Pascal and Delphi, but the only formal trainig I ever had in coding, was ANSI C based.) However, there seems to be little to no standardisation in the way the various compilers are invoked, or how the build time parameters are set, not least from within the source code, let alone via any third party IDE via a command line shell. (Code::Blocks, or the MPLAB IDE) The result, is to make what is otherwise an "Open" source project, very much "Closed" if you don't have the particular compiler/environment the original author had, and also don't have the detailed in-depth knowledge of that, and the tools you happen to have found and placed in front of you. I have just found that this project references an include file that is native to the original compiler, that I don't have. The ubiquitous "string.h" Googling shows so many variations and just the references, not the file. Not that I even know the version of ccs compiler the original author used, and anyway, I'm not likely to shell out what ccs want for a compiler suite, for a one time build, purely for my own use. Yes I know they do a demo, guess what, it loads OK, but wont run saying that the demo period has passed, not that I ever had it installed before. I have mailed (several times) CCS, only automated messages in return with a reference number, no help at all. Showstopper time for now sadly, if just because I've run out of available time to mess with all this, I obviously spent too much time trying to figure it out myself, before coming here... Teach me to build the hardware before getting the code working. Thanks for the hints and help so far, I'll go back to lurking. Cheers. Dave B. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
