Hello, could you please try the solution that Waffle has posted above and see if it works? Thank you.

Misunderstood issue. He's requesting more advanced #include preProcessor support for CfgFunction functions. Currently #include will only include a file that can be found within the function's directory. He's requesting the ability to search for files lower in the directory tree.

I was thinking about something like I am already using:

• I define functions in some files
• I include all these files in the init.sqf (with #include)
• Before the inclusion of function files, I include all definition files (eg the ones containing #define blabla or even other #include)

This way I don't care where the definition file is located since it is included in the init.sqf and all file paths are visible at this level.

So I am asking whether this can be achieved with CfgFunctions.

One example is that I have a list of colors as #define in a file ([root]\colors.ext and I want to use this in [root]\functions\fn_myfunc.sqf and also other scripts that i don't want to place in same folder as fn_myfunc.sqf but sth like [root]\mygreatscript\toto.sqf. At the moment I'm forced to cpy the colors.ext file in [root]\mygreatscript\ and [root]\functions\.

You can create a function to act the same as a #include

I don't see how to do that (please give an example).
Do you mean I should use variables instead of #define? If yes then I will still have to use 2 files colors.ext (with #define, used in dialogs) and color.sqf (with variables used in sqf scripts).
Also my point was to use #define for all variables that are static.

The status of this ticket is incorrect because I already provided more informations

Fixed on dev, rel path is now supported https://community.bistudio.com/wiki/PreProcessor_Commands#.23include