Re: Could not open hla.hw
- From: Frank Kotler <spamtrap@xxxxxxxxxx>
- Date: Sun, 27 Aug 2006 06:57:41 -0400
plain wrote:
Frank Kotler wrote:
plain wrote:
....
"Could not open hw.hla"
To rule out the obvious, first... does "hw.hla" exist? Not unusual for
"helpful" editors to save your file as "hw.hla.txt"...
Best,
Frank
Thank You Frank:
For getting back to me. I was careful to ensure .txt wasn`t
appended to hw.hla.
Too bad. That would have been easy. :)
Though the documentation doesn`t mention adding
directories to "User Variables" instead of only "System Variables"
where the files now reside , I did even copy paths from System to User
in hopes I had left something out. No luck.
I'm not sure what you mean by "system variables" and "user variables"... Does XP keep 'em separate? In any case, I don't think this is a "path problem". You'd get "no such file or command" if the PATH wasn't right, and a slew of errors if the include or library files couldn't be found.
I am puzzled by one thing
however: In System Variables the "lib" path has a semicolon in front
of it. I did try removing this semicolon which of course did nothing.
Why is this line there? doesn`t the semicolon remark out this path in
some languages?
Some languages, yeah, but it's a delimiter in environment variables (Linux uses colon). I wouldn't expect to *start* with a semicolon, but it probably wouldn't hurt. The "LIB" variable isn't one of hla's anyway. HLA needs "PATH" (hla, hlaparse, your assembler, and your linker need to be on the path), "hlainc" (which points to a directory), and "hlalib" (which points to a specific file, not a directory). In Linux, these are case sensitive and need to be lower case.
I`m new at all programming so you have an uphill
battle
helping me, however, I do appreciate it.
The message "could not open hw.hla" leads me to believe the file is
being recognized, right?
Well... It's a good sign - means that hla.exe and hlaparse.exe are on your path and running. Means that hla has added the ".hla" extension to the "hw" you told it (wouldn't expect hla to screw that up). If it were a "permission" problem, it'd probably say "access denied" or something. Generally "can't open" means that it wasn't saved *where* you expected, or wasn't saved under the name you expected. (or wasn't saved at all...)
What should happen after that?
What should happen is that hla and hlaparse conspire to compile your file into "raw" assembly language - hw.asm, hw.data.inc, (several .inc files like this) - then should call your assembler to assemble it into hw.obj (or hw.o) - the should call your linker to link your .obj file(s) and hlalib.lib (or hlalib.a, in Linux) into an executable.
If "hw.hla" exists, in your current directory, I'm stumped why HLA wouldn't open it. You could try Nathan's "copy con: myfile.hla" idea (real programmers do "copy con: shrinkwrap.box" :) That just copies what you type to the file. Will eliminate any "editor errors" anyway!
It's a frustrating stage, not being able to get "hello world" to compile. Hope you get past it soon!
Best,
Frank
P.S. The subject line, and one part of your first post, referred to "hla.hw". The file should be "hw.hla". Then you type "hla hw", HLA adds the extension, and assembles "hw.hla" (we hope). If the file is really named "hla.hw", it won't work... just to make sure...
.
- References:
- Could not open hla.hw
- From: plain
- Re: Could not open hla.hw
- From: Frank Kotler
- Re: Could not open hla.hw
- From: plain
- Could not open hla.hw
- Prev by Date: Re: Could not open hla.hw
- Next by Date: Re: Any explanations
- Previous by thread: Re: Could not open hla.hw
- Next by thread: Re: Could not open hla.hw
- Index(es):
Relevant Pages
|
