Aut2exe compilation error

[ur]

I am trying to compile below au3 file using aut2exe but getting this error.

#include <FileConstants.au3>
#include <MsgBoxConstants.au3>
#include <WinAPIFiles.au3>
#include <array.au3>
#include <Date.au3>

$sDate = "2020-11-23"
$sLicenseCode = "Input1"

Func checkValidDays($sDate)
    MsgBox(0,"", _NowCalcDate())
    ;$days_finished = _DateDiff('D',"2020-11-23",_NowCalcDate())
    $days_finished = _DateDiff('D',$sDate,_NowCalcDate())
    if $days_finished > 0 Then
        MsgBox(0,"","Date expired!!")
        Return False
    Else
        MsgBox(0,"","Still "& Abs($days_finished) & " left.")
        Return True
    EndIf
EndFunc

if checkValidDays($sDate) Then
    RunWait("erwin.exe -LIC "&$sLicenseCode,"C:\Program Files\erwin\Data Modeler r9")
EndIf

Command I used.

C:\Users\UDAYKI~1\AppData\Local\Temp\LicenseApplicator>Aut2exe_x64.exe /in LicenseApplicator.au3 /icon erwin_favicon_32x32.ico /out LicenseApplicator.exe /nopack /x64 /gui

I copied the Aut2exe_x64.exe to that folder to compile.

With, UI Build option or compile option from scite editor, I am able to compile but not from here.

---------------------------
Aut2Exe Error
---------------------------
Line 1  (File "C:\Users\UdayKiranReddy\AppData\Local\Temp\LicenseApplicator\LicenseApplicator.au3"):

#include <FileConstants.au3>

Error: Error opening the file.

---------------------------
OK   
---------------------------
Any suggestions please.

 

[Nine]

You need to copy all #include files locally also.

[ur]

yeah, can we change the <> path to the include folder we copy in the current folder instead of changing every include statement to "./"

[ur]

Thanks for the input. My issue got resolved.

Including folder is not supported in FileInstall.

So, I am unzipping it on the temp folder and including from there

[mLipok]

1 hour ago, ur said:

So, I am unzipping it on the temp folder and including from there

But why ?

1 hour ago, ur said:

yeah, can we change the <> path to the include folder we copy in the current folder instead of changing every include statement to "./"

Take a look for AutoIt3Wrapper directives .

 

[caramen]

You could specify the folder from where your file should be included. 

#include <FileConstants.au3>

;Could be : 

#include <C:\MyFolder\FileConstants.au3>

But it can become very fast, a big pain to maintain things like that when you will need the file again. 

There is also no reason to do thing like that. 
Because if you compile a script with an "include"

The included file will be in the compiled executable as a part of your code. So there is no need to externalize it. 

Edited November 26, 2020 by caramen

[mLipok]

If you want to do this in this way.... 

#include <C:\MyFolder\FileConstants.au3>

that is not properly usage. 
Try this form instead:
 

#include "C:\MyFolder\FileConstants.au3"

 

https://www.autoitscript.com/autoit3/docs/keywords/include.htm
 

Quote

Using #include <>

Standard library	The path of the currently running interpreter with "\Include" appended is searched.
User-defined libraries	The registry value mentioned above is read and each directory is searched in the order they appear in.
Script directory	The directory of the currently executing script.

Using #include "" (This is the reverse of #include <>).

Script directory	The directory of the currently executing script.
User-defined libraries	The registry value mentioned above is read and each directory is searched in the reverse order they appear in.
Standard library	The path of the currently running interpreter with "\Include" appended is searched.

 

[mLipok]

20 hours ago, mLipok said:

But why ?

 

22 hours ago, ur said:

I copied the Aut2exe_x64.exe to that folder to compile.

With, UI Build option or compile option from scite editor, I am able to compile but not from here.

Are you trying to compile this script on a computer that does not have AutoIt and SciTE4AutoIt installed?

If so ...... did you try this:
https://www.autoitscript.com/wiki/FAQ#AutoIt.2BSciTE_Portable_Developer_Environment

 

 

Edited November 24, 2020 by mLipok

[Jos]

Can somebody make clear to me why there is any need for moving/copying files at all? When it works from SciTE it works from the command line as that is what SciTE/AutoIt3wrapper does.?

Edited November 29, 2020 by Jos

[mLipok]

4 minutes ago, Jos said:

When it works from SciTE it works from the command line as that is what SciTE/AutoIt3wrapper does.?

Unless he do not install AutoIt at all.

 

[Nine]

31 minutes ago, mLipok said:

Unless he do not install AutoIt at all.

I think this is the objective.  Based on this other thread, he wants to deploy a script.exe that will be creating a new exe from scratch on computers not having AutoIt installed.  This is why he needs to copy everything into a single folder (aut2exe.exe, includes, au3, ico, etc) and then launch the compiler.

[mLipok]

@ur

What is the main reason for doing it this way ?

..... again problem with debuging and ScriptLineNumber ? Or with AV software ?

Why you can't normally compile to EXE or  A3X ?

 

Edited November 24, 2020 by mLipok

[caramen]

Too much "why". In this thread 🤣

[ur]

On 11/25/2020 at 1:13 AM, mLipok said:

@ur

What is the main reason for doing it this way ?

..... again problem with debuging and ScriptLineNumber ? Or with AV software ?

Why you can't normally compile to EXE or  A3X ?

 

The reason is, one customer is asking to have a form which he could fill the details, based on the details it should create a exe on his machine.

So, for the embedded exe, I have added the Aut2exe_x64.exe and the required include files.

Now, as the size is less, I have included the complete include folder as zip file and extracting those contents in the temp folder and deleting it after the work is done.

 

 

[ur]

Thank you very much all for your inputs. One more doubt, is there any utility to get list of all dependent files we are including. So I could use that instead of embedding the complete include folder.

Edited November 29, 2020 by ur

[mLipok]

Include dependency tree

In my signature 

[ur]

Thank you @mLipok