Compile includes aren't working with dynamic path

[Grovkillen]

See this example and you will only have the second "HELLO" working if you compile it as an exe.

If you open it in the same directory as the "test_1.scp" you will get an error. Opening it in a separate (otherwise empty) directory and you only get the second "HELLO".

test_main.scp (compiled as exe with the option "compile includes" selected):

Code: Select all

Let>TEST_DIR=%SCRIPT_DIR%
Include>%TEST_DIR%\test_1.scp
Include>%SCRIPT_DIR%\test_2.scp

test_1.scp:

Code: Select all

MDL>HELLO 1!

test_2.scp:

Code: Select all

MDL>HELLO 2!

My guess is that the compiler isn't parsing through the code to see what value the variable got once reaching the includes command but instead treat it as a string if it's anything other than explicitly declared %SCRIPT_DIR% or any other system variable.

I hope this can be resolved since I'm relying on having the import path dynamically to fetch the includes from different path's for different projects.

[Dorian (MJT support)]

Have passed this on.

[Grovkillen]

I wouldn't mind if I need to declare a variable from within the compiler settings. Kinda like how we add the output exe file and icon. If this is easier to do. But in any case the compile includes need to be documented since I didn't get any warnings or script errors.

[Marcus Tettmar]

Note:

https://www.mjtnet.com/manuals/v15/HTML/create-exe.html

Compile Includes: "Scripts referenced by Include> statements will be embedded and compiled into the Exe. Will not work where Include> references scripts via variables other than SCRIPT_DIR."

[Grovkillen]

Aha, got it. I will make a build script that will temporarily replace those lines.

Perhaps it should be noted in the help for "include" as well?