#SAS C Disappointing!
4 messages in this thread
[ continuation ]
support working in project directories with out editor/compiler file
copying into the working directory?
wmc
Wayne,
I, like some of the other responses to your message, do not use LSE, and
based on the few looks I've had at it, would recommend almost anything else
instead. I also haven't really looked at the Workbench-interface stuff for
the Lattice compiler, as it is all brand new with this update. I've been
using Lattice from a CLI for so long that it's real hard to break old
habits (and I'm not convinced that the iconic approach is really right for
development anyway).
I'm sure that there is probably something you've missed in the setup,
however. I know that you don't need all of your files (including the SAS
executables) in your current directory. Guessing here, but do you have LC:
assigned to the "c" directory containing the SAS executables? I'm pretty
sure the "project" icons used by SASCSETUP all reference LC: for their
tools. Also, it might be the case that LC: needs to be in your PATH prior
to doing the LoadWB in your startup-sequence.
Hope this helps.
…BobR
White Wolf Productions
Bob,
I learned again that the assignment I did from a little iconx script didn't
cut it as far as establishing the LC: path – I had to embed it in the
startup sequence. As long as I use the lse icon in the LC: directory I'm
ok. If I use the icon to invoke lse in any of the SASCSETUP sub directories
of LC:, the link will fail with phony messages that indicate teh hrddrv
partition that LC: is on needs to be "inserted"! So it looks like I'll just
use it from the LC: directory until I find a replacement. What I'm used to
is the editors ED, Memacs and the M2E of M2Sprint.
wmc
Wayne:
I have had many of the problems you describe while trying to invoke the
compiler from the Lattice 5.04 version of LSE. If you find the correct
manner of setting up the assigns and the associated files so the compile
process works, please let me know. Thanks.