Lattice Front-end tools?
32 messages in this thread
I remember reading this, but I need confirmation. Does the latest version
of Lattice C come with any front-end CLI utilities that make it more
"friendly" to those of who are used to UNIX compiler tools?
Steve
The latest version of Lattice C is 5.05.
However, SAS/C, its successor, is up to version 6.2.
SAS/C doesn't come with utilities to make it look particularly like
the UNIX compilers, but there is a PD file in listings here called
ucc.lzh which accepts UNIX style compiler options and invokes the
SAS/C front-end for you.
–Doug
Thousand pardons for the mistyped product name, and thanks for the info on
ucc.lzh. I'll grab it. Now all I have to do is dig out that upgrade
sheet I got a while back.
Thanks!
Steve
Steve,
for those of us who have NO IDEA what 'UNIX compiler tools' are, a list
would be most helpful. Maybe a short summary of what these tools do would
be useful also. I've been using SAS C since the 1000 days, and am pretty
familiar with it's capabilities are and the tools that come with it.
(un)Fortunately, I've not used UNIX for more than an hour.
Basically, I'm just talking about "cc" and "ld". I realize that SAS/C has
those equivalents in "lc" and "blink", but I like the UNIX syntax…
basically since I've been using it since 84. They don't require any extra
files to be around for options, everything can be done within a few lines.
In fact, you can just link everything using cc, which eventually calls
ld.
I've owned SAS/C for some time now. Every time I try and get used to the
alternate syntax, it just drives me wild. I think it's really just
"blink" that I'm ticked off about, more than anything else. I just can't
fathom what the correct incantation is from the supplied docs. I'm used
to just saying things like "cc -o foo foo.o main.o bloop.o -lm" to get an
executable to pop out.
Sure, I can make changes to OS kernels, dive into NFS/networking code to
fix bugs, and I can write new features for window managers, but "blink"
leaves me baffled. 🙂 I'll grab the "ucc" stuff, I'm sure that will
help. I've been trying to become one of the converted for a long time now
(really!), and I'm hoping that will help. There are some features I'm
really looking forward to using.
Anyway, that's the long and short of it. (ha! A pun!…ahem…)
Steve
Well, I just ordered the SAS C upgrade (from 5.10a to 6.2) today, so we can
battle it together.
I should point out that the package you get will have Version 6.0
in it. All customers get 6.0 so we know that everybody has the
same base set of diskettes; you should get the patch to 6.2
from here, another BBS, or ask the sales or tech support people
for a diskette.
It's important that everybody have the base 6.0 diskettes, since
all patches read the original diskettes and apply the changes
to the files on the originals.
The advantage of this method is shown by the fact that you don't
need to apply the 6.1 patch to apply the 6.2 patch. Since both
are relative to the base diskette set, 6.2 is independant of 6.1.
–Doug
You mean they won't include the 6.2 patch disk unless I specifically asked for
it? I think I did ask for the upgrade to 6.2…
The diskettes in the box will be 6.0.
I'm not sure if the 6.2 patch diskettes have made their way to
distribution yet; if they have, you'll get a seperate patch
diskette independant of the ones in the box. If not, you'll
be getting a letter telling you that the patch is available
and offering to send you a diskette if you don't already
have it.
–Doug
And of course I can download the patches from the library here, right?
Exactly.
–Doug
Doug,
Are all users supposed to be getting a letter telling us about the 6.2
patch disk being available? I don't remember getting one for 6.1, and
haven't seen one yet for 6.2.
Can you check into this? I can't afford to download the patch file!
73, Kelly
Kelly,
We didn't announce 6.1 on the theory that users who weren't having
problems didn't need it, and users who were having problems would
contact tech support. We'll send you a free 6.2 disk if you contact
tech support – which you can do from CompuServe via EMITS (see chapter
3 of your user's guide, volume I).
We are still in the midst of preparations for a general mailing
about 6.2. We are planning a new method of contacting tech support
and hope to announce it in the same letter; thus, the 6.2 letter
hasn't gone out yet. (All the old methods are still good, this
would be a new one.)
There may or may not be a 6.3 at this time. A couple of bugs have
been reported, one of which I'd really like to see fixed, but in
general 6.2 has been pretty stable and I'd recommend contacting
tech support to get it. BTW, have you tried looking on your local
BBS's or at your local user's group? The patch is freely
redistributable, so anybody who has a copy is a distribution
point for you – just get a copy of what they downloaded.
–Doug
Doug,
Thanks for the reply.
Okay, I'll look into requesting the disk via EMITS.
local BBS – can I break down laughing now? There is a very small local
BBS (I have never visited it – clone oriented), but doubt there is an
Amiga BBS within 500 miles of here that would have any half decent files
on it.
73, Kelly
Kelly,
Where are you? There are BBSs all over the place in NC, even though
we have no Amiga dealers!
–Doug
Doug,
Have you guys fixed that optimization problem with the delete character
sample I sent you? We _still_ have to turn the optimizer off for a couple
modules in MetaScope.
Vic,
I have no idea – I don't even remember the problem. You'd have to
contact tech support. (I have a really lousy memory for bugs like
that.)
–Doug
Doug,
I'm still using 5.10. I never got a mailing about 6.0, and now you're
talking about 6.3??? What's included in the upgrade? How much?
Steve
Steve,
If you didn't receive an upgrade notice, you're not on our mailing
list and you need to contact our Book Sales department to get reinstated.
SAS Institute Inc.
Book Sales Department
SAS Campus Drive
Cary, NC 27513
USA
The upgrade price from V5.10 is $109, which gets you a brand-new 6.0
package, complete with 1200 pages of rewritten manuals and a LOT of
development effort. Patches are available on CIS and elsewhere in
the freely redistributable software arena to bring 6.0 up to version
6.2. We are currently considering doing a 6.3 patch, but haven't
come to a decision yet (patches delay work on new products, so we have
to weigh these decisions carefully.)
–Doug
Is there another bug fix ready to com out ?? (Please excuse My english) Ciao
MB-)
Massimo,
We are considering doing a 6.3, but haven't decided yet. Any patch
releases delay work on new products, so it's a big decision.
–Doug
Good. The 6.2 is working flawlessy. I am trying to use the parnet.device to
build something like a remote shell, but I have found only a include file. Can
you tell me something useful to me ? Is the parnet.device source available
somewhere ? parnet.device is from Matt Dillon.. right ?? Is already running
software distillery BBS ?? Ciao MB-)
Hmm…I better get on the stick and order the upgrade Monday then. I
still have 5.1<something>
Steve
With 6.0, it's now SC and SLINK instead of LC and BLINK.
Also, you don't need to leard SLINK at all. The SC command does it all
for you – invokes the compiler, invokes the assembler, invokes the
linker. If you get that UCC command from listings, it'll take UNIX
options and do it.
To compile and link "hello.c", you type
sc link hello.c
As far as options files go, we have never REQUIRED an options file –
it has been available for convenience. I find it very convenient to
keep most of the compiler options in the file, maintain them with
the SCOPTS utility, and invoke the SC command on the individual
files using SMAKE (the successor to the LMK make utility) with
no options. When it comes time to link, I use the SC command
again with the LINK option, and simply feed it all the .o files
and libraries.
6.0 SCOPTS allows you to add options to the file by typing them on
the command line, too – you don't have to use the mouse if you don't
want to. Think of the file as changing your compiler's defaults.
I think you'll find SC to be much nicer than the old LC. The options
are English words, so they are easier to remember; the SCOPTS
program has online help for each option, just put the mouse over
the option's button and hit HELP; most options have a positive and
a negative version, using the prefix NOxxx for the negative version,
and there are NO TOGGLES like there were on the LC command.
–Doug
Thanks for the info. My order for the upgrade will go out Monday. Unless
someone is there this weekend, of course. 🙂
I couldn't find the ucc.lzh stuff online here. If you have it, would you
be able to upload it?
Steve
Sure, I can upload it. After all, I wrote it 8^)
–Doug
Shouldn't the pun have been?:
"Anyway, that's the long and short of int."
<smmiiille>
BTW, I always make a make file (I use the GNUmake available here in the
LIBS, not 'smake').
Ha! You're such a char-acter. 🙂
Steve
I use exactly ONE command when running the C compiler and linker 'make' I use
Steve Andersen's adaptation of gnuMake because it's more powerful than 'slink'
Nice to know you still care Vic… Although, I think that you've made enough
fixes to GNU Make that it is no longer mine – it's yours!
Steve
Steve,
I've got some interesting 'enhancements' to RCS also which aren't quite
irond out. I'll be doing a MASSIVE upload one of these days (weeks,
months…we're swamped) when I get them straightened out. Hmm, I should
prolly EMail the GNU folks about some of the enhancements, make sure they
conform (assuming that they'll think they're as good as I do <smmiiille>).
Vic: Re your RCS enhancements: I'd be interested in getting a copy from you. I
did manage to get RCS 5.6 to build under SAS/C 6.0 – I actually dropped my
earlier port and started from the original Unix source, then put in the
Amiga-specific stuff as needed. Seems to work OK, but doesn't have any of your
enhancements. I still don't spend much time on the Amiga (I guess I'm becoming
a PC/Windows convert, but still wishing it was as cool as AmigaDOS), but I am
interested.
Steve