Jump to content

Issues moving the default UDFs


 Share

Recommended Posts

Hi all,

 

I'm trying to put a full project on git, and it has been requested that the libraries required are part of the repository, so that anyone doing a pull will have everything they need to build.

I have made a copy of the files used, and referenced them correctly in the script (I think), However, the compiler still seems to look at the original files in the default "Include" directory where AutoIT installed..

The attached image shows errors during compilation, where it would appear that after using the library in the location specified, it is also looking at the installed version. Both of these begin with #include-once, but it appears to be trying to re-define all of the constants for EVERY one of the included files

 

Can anyone explain? Or suggest a better way to package things on git?

 

Many thanks

 

 

Capture.JPG

Link to comment
Share on other sites

Not sure why you are getting these errors. Have you checked to see if the UDFs contain code to include other UDFS?

The bigger question in my mind is why you would do all of this in the first place. Anyone downloading the script would need AutoIt to compile / run it. Therefore, wouldn't they already have a set of the default UDFs?

Link to comment
Share on other sites

Hi. 

I guess #includes inside UDFs will lead to this errors. Your main script loads the UDFs from a path you changed to. Then includes inside a called UDF is loading the same UDF again. 

Right, there is #include-once but the pathes to the UDFs/includes are different. So I guess #include-once can’t work as you think and they will called twice. 

Regards, Conrad 

SciTE4AutoIt = 3.7.3.0   AutoIt = 3.3.14.2   AutoItX64 = 0   OS = Win_10   Build = 19044   OSArch = X64   Language = 0407/german
H:\...\AutoIt3\SciTE     H:\...\AutoIt3      H:\...\AutoIt3\Include     (H:\ = Network Drive)

   88x31.png  Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...