Difference between revisions of "Loading Order of Lua Files"
From GiderosMobile
(added some more explanations) |
(added some more explanations) |
||
| Line 11: | Line 11: | ||
</source> | </source> | ||
| − | '''PS: the path is relative to the file in which you call --!NEEDS:''' | + | '''PS: the path is relative to the file in which you call --!NEEDS:''' (unless your path begins with a /) |
This will tell Gideros to load '''your_file.lua''' before the file containing the above code. | This will tell Gideros to load '''your_file.lua''' before the file containing the above code. | ||
| − | To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write: | + | |
| + | The other Gideros Code Dependency you can implement by code is the exclude file. To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write: | ||
<source lang="lua"> | <source lang="lua"> | ||
--!NOEXEC | --!NOEXEC | ||
Revision as of 00:14, 27 September 2020
Supported platforms: 
Available since: Gideros 2020.5
Description
You can now implement Gideros Code Dependency by code instead of Gideros project setting.
--!NEEDS:your_file.lua
PS: the path is relative to the file in which you call --!NEEDS: (unless your path begins with a /)
This will tell Gideros to load your_file.lua before the file containing the above code.
The other Gideros Code Dependency you can implement by code is the exclude file. To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write:
--!NOEXEC
This is very useful if you develop a Lua library that is meant to be used in several projects.
Example
--!NEEDS:luashader/luashader.lua
local function makeEffect(name,vshader,fshader)
...
end
See also
Methods |
EventsConstants |
