Environmental variables in #include?

[olo]

Can one put a windows environmental variable into a #include at the top of there script.

Reason why I wanna do this is basically so my script can run on other pc's and not rely on a hardcoded specific file path such as "C:Usersblablabla"

[guinness]

Use relative paths instead. Also instead of asking first, why not try it?

Edited May 17, 2013 by guinness

[olo]

Use relative paths instead. Also instead of asking first, why not try it?

 

I have tried it and could'nt get it to work

So was wondering if there was another way around it.

You dont have to help me but dont come on and criticize. Please its annoying...

Edited May 17, 2013 by olo

[JLogan3o13]

You might include that, then. Something like:

   "Is (xyz) possible? I tried it by doing (abc), but couldn't get it to work."

Then at least we can see what you've tried, rather than guessing

[olo]

You might include that, then. Something like:

   "Is (xyz) possible? I tried it by doing (abc), but couldn't get it to work."

Then at least we can see what you've tried, rather than guessing

Here is what I have:

#include <C:\Documents and Settings\User\Desktop\Library\Error_log.au3>
 
;Here is what I wanna do though
Global $var = EnvGet("USERPROFILE")
#include <$var\Desktop\Library\Error_log.au3>

[water]

#include is a directive which is processed before any variables are set.

So: No you can't do it this way

Wouldn't it be easier to distribute the compiled script?

[guinness]

Olo,

That's not criticising, if you had posted the code in your first post then we wouldn't be 5/6 posts down. But you're right about one thing I don't have to help you, though I will...you can't use variables like that as they're created when the script is compiled and running. Did you try?

#include <%USERPROFILE%\Desktop\Library\Error_log.au3>

If I had to criticise though, it would be learn to post more detailed support questions in future.

Edited May 17, 2013 by guinness

[olo]

Olo,

That's not criticising, if you had posted the code in your first post then we wouldn't be 5/6 posts down. But you're right about one thing I don't have to help you, though I will...you can't use variables like that as they're created when the script is compiled and running. Did you try?

#include <%USERPROFILE%\Desktop\Library\Error_log.au3>

If I had to criticise though, it would be learn to post more detailed support questions in future.

 

Very well. Your a gent anyway for the help!

[olo]

#include is a directive which is processed before any variables are set.

So: No you can't do it this way

Wouldn't it be easier to distribute the compiled script?

I suppose it would but its like a tree. Its got all sorts of other scripts feeding into the main one.

[guinness]

If you want to distribute, then use ... to strip the includes into one file.

#Obfuscator_On
#Obfuscator_Parameters/StripOnly

[olo]

Olo,

That's not criticising, if you had posted the code in your first post then we wouldn't be 5/6 posts down. But you're right about one thing I don't have to help you, though I will...you can't use variables like that as they're created when the script is compiled and running. Did you try?

#include <%USERPROFILE%\Desktop\Library\Error_log.au3>

If I had to criticise though, it would be learn to post more detailed support questions in future.

 

I tried your line of code and it just gives me a cant open file error

[water]

If you distribute compiled scripts you do not need to install AutoIt on every PC, users can't modify the script etc. A lot of advantages.

[olo]

If you distribute compiled scripts you do not need to install AutoIt on every PC, users can't modify the script etc. A lot of advantages.

 True that. But my boss would like to run it on his win7 machine while im on winxp. Also he'd like to modify it as he sees fit.

[water]

I tried your line of code and it just gives me a cant open file error

Guinness just told you to try. He didn't say it works

[guinness]

Guinness just told you to try. He didn't say it works

Thanks water! -_0

[water]

 True that. But my boss would like to run it on his win7 machine while im on winxp. Also he'd like to modify it as he sees fit.

Two persons playing around with the source code on different machines? What a nightmare!

[olo]

Two persons playing around with the source code on different machines? What a nightmare!

Tell me about it. He wants others from the team to join in aswell. There's just no pleasing the man... :/ ah well life sucks

Edited May 17, 2013 by olo

[guinness]

Have you not told your boss that maybe subversion control is the way forward?

Edit: It's how water and I (plus the other Devs/MVPs) update the AutoIt source code and UDFs. Otherwise doing it all via PM/e-mail would be a logistical nightmare.

Edited May 17, 2013 by guinness

[olo]

Have you not told your boss that maybe subversion control is the way forward?

We are doing that. My script get put onto tortoise svn where others can download it and play around with it.

[water]

No nightmare then