BugFix Posted June 3, 2013 Share Posted June 3, 2013 So far I have always Lua scripts included with dofile() in other scripts. That works, like expected. Because loading files with "require" is more flexible, i've tried to do that with my scripts. I've added in the Lua startup script my pathes to package.cpath. I'm using the property "Lua.User.Scripts.Path" and so i've added: props["Lua.User.Scripts.Path"].."?.lua;" and props["Lua.User.Scripts.Path"].."??.lua;". So it works for "..test.lua" and also for "..testtest.lua" - pathes. I've a simple script for testing: file: test.lua writeA = function() print( 'A' ) end writeB = function() print( 'B' ) end If i use: dofile(path_testfile) in another script, i've access to this functions. By using: require "test", i get an error: error loading module 'test' from file 'C:Code_AutoItLUAtest.lua': %1 is not a valid Win32 application. If i use require with the file "alien.lua" it works. But i can't see basicly differences in structure between the scripts. What am I doing wrong? Thanks in advance. Best Regards BugFix Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now