%ORANGEC% in *.cfg is not correctly expanded about orangec

[LADSoft]

Hi,

I didn't realize there was such a thing as windows 7 starter until you
pointed it out :). Hopefully it isn't so badly mangled that it can't
handle environment variables...

The tools are supposed to utilize environment variables in the .CFG
files. So ORANGEC is an environment variable that has been previously
set up. For example:

set ORANGEC=c:\orangec

So you would have had to either set it up yourself as an environment
variable, or let the install package set it up for you. But I think if
you install it from the install package, you would have to explicitly
set the option to run from the command line to get it set up...

David

lionfaith wrote:

I tried to compile a little sample through command line and had errors:
Error factorial.c(3): Cannot open include file "stdio.h"
Warning factorial.c(12): Call to function 'printf' without a prototype
in function main
Warning factorial.c(13): Call to function 'scanf' without a prototype
in function main
Warning factorial.c(16): Call to function 'printf' without a prototype
in function main
Warning factorial.c(20): Call to function 'printf' without a prototype
in function main

I replaced %ORANGEC% variable in occ.cfg with the actual path to
OrangeC directory and occ then reported linking error:
Error: Input file 'c0xpe.o' does not exist.
Warning: Library 'climp.l' does not exist
Warning: Library 'clwin.l' does not exist
Error: Undefined External printf in module C:\dev\c_tests\hello.c".

I made the same modification in ocl.cfg and olinker.cfg and now it
works fine. I suppose %ORANGEC% didn't get expanded. By the way, if it
helps, my system is a Winwows7 Starter.

—
Reply to this email directly or view it on GitHub
#3.

[lionfaith]

Hi!
That's it! I was using the zipped version of the package hence ORANGEC wasn't set. It is now and it all works fine. Is the need for such a variable mentionned anywhere in the documentation? I might have missed it.
Thanks for the nice and fast answer,
Lionel

[LADSoft]

Hi,

glad that was it! It is mentioned briefly in c:\orangec\readme.txt,
but maybe I ought to make it more obvious :)

David

lionfaith wrote:

Hi!
That's it! I was using the zipped version of the package hence ORANGEC
wasn't set. It is now and it all works fine. Is the need for such a
variable mentionned anywhere in the documentation? I might have missed it.
Thanks for the nice and fast answer,
Lionel

—
Reply to this email directly or view it on GitHub
#3 (comment).

[lionfaith]

Hi,
my fault actually, I haven't read orangec\readme.txt. Instead, I've mainly read orancec\help*.chm. When I got stuck with my problem, I've sought for the solution in orangec\help\tools.chm at "OCC compiler" topic, "specifying include path" page. I've also searched orangec\doc. I hope those informations will help :)

Lionel

[LADSoft]

I'm adding a comment about this in the places you searched :)

[lionfaith]

Big thanks. I'm sure it will help future like me. :)