(Solved) Include a3x Issues

[seadoggie01]

When compiling a file to a3x I kept running into issues... I was getting messages that were saying that I was attempting to redeclare a constant. The strange thing was that everything worked fine with the au3 version. So I cut out all the lines of code and ended up with these two files that are the base of the issue.

Test_1.au3

#include <Array.au3>
#include <Test_2.a3x>

ConsoleWrite("Test_1" & @CRLF)

Test_2.a3x

#AutoIt3Wrapper_Outfile_type=a3x

#include <GuiTreeView.au3>

Msgbox(0, "A3X", "I ran!")

When I run Test_1.au3 (not compile) I get this error: <FullFilePath> (3830) : ==> Can not redeclare a constant.:

If I remove either of the includes, everything works great. Anybody have any clues as to what could be happening here?

 

(Btw... normally including Excel and GuiTreeView works great and these UDF are amazing! Not dissing the authors at all )

Running Windows 10 x64, Full version of AutoIt and SciTE, default compiling to x64, but x32 doesn't seem to matter, I tried

 

Edit: Excel includes Array.au3, replacing Excel with Array.au3 continues the issue

Edited August 19, 2019 by seadoggie01

[seadoggie01]

Found it... also, can I get a big F in chat?

 

Including files in the a3x caused a chain reaction of includes... resulting in the AutoItConstants.au3 file to be included in both files. When the resulting program ran, it found the constants double included and (of course) errored. I think i'll need to use Tidy or Stripper settings to replace constant variables with actual values. Leaving this here for anyone else that stumbles across this

[jchd]

In current release, AutoItConstants.au3 first line is #include-once so it shouldn't be a problem if it gets included more than once.  Proof:

#include <AutoItConstants.au3>
#include <AutoItConstants.au3>
#include <AutoItConstants.au3>
#include <AutoItConstants.au3>

MsgBox(0, "", "")

Are you running the latest release?

[seadoggie01]

Yes (I'm on v3.3.14.5) ... it's because I was including a separate a3x into a au3 file and they don't check between them if the other has something included... like this

File 1 (compiles to exe)

#include <Array.au3>
#include <File2.a3x>

ConsoleWrite("I'm au3 or exe!" & @CRLF)

File 2 (compiles to a3x)

#AutoIt3Wrapper_Outfile_type=a3x

#include <Array.au3>

ConsoleWrite("I'm a3x" & @CRLF)

It will give you an error about having duplicate functions or constants... I think because the check is made before inserting the second file... or because it would need to be recursive... I'm not sure

Edited August 19, 2019 by seadoggie01
Adding AutoIt version

[jchd]

I never imagined you could have a mixed-format ( .au3 + a3x) being run or built.

[Skysnake]

13 hours ago, jchd said:

I never imagined you could have a mixed-format ( .au3 + a3x) being run or built.

I do that all the time

Problem is when the same file gets included twice in different formats. You won't see the problem during the build, only at runtime.

 

[jchd]

FMI, what is the use case for doing so?

[mLipok]

How you bulid them?

Could you make an example reproducer? 

[Skysnake]

41 minutes ago, jchd said:

FMI, what is the use case for doing so?

The answer is simple enough.  The obsession to keep code private.  Keep includes in standard .au3 and compile own code to .a3x

 

Problem starts when you compile includes. Like GUIConstants

[Melba23]

Hi,

I can see why the problem arises - and I cannot really see how to avoid it without user input.  When you compile a script into an .a3x file all of the #include files are expanded and so there is no indication to any subsequent run or compilation which includes that file that these #include files are there as there are no "#include-once" lines to find.

As suggested above, the only solution I can see would be to get the .a3x file running with the necessary includes and then compile it with all the includes commented out - you will need to disable Au3Check to do this. Then make sure that the script in which the .a3x file is an  #include has those necessary includes within it before the .a3x file itself.

But given that an .a3x file is as easy to decompile as any other compiled AutoIt file I have to question whether the faff involved in doing all of the above is actually worth it.

M23

[jchd]

2 minutes ago, Melba23 said:

I have to question whether the faff involved in doing all of the above is actually worth it.

I too have hard time seeing the light out of all this.

[seadoggie01]

I was trying to use it because the anti-virus here at work picks up any 32bit scripts I write. I wanted to control a 32bit application with a listview, however, so I was trying this...

Main File_x64.exe or au3

       FileInstall: ProgramControler_x32.a3x

Instead I found I can do this much easier...

Wrapper_x64.exe

     FileInstall: AutoIt_x32.exe

    FileInstall: MainApplication.au3

 

I like the idea of open source, so compiling to a3x had nothing to do with hiding code, I don't care who reads my stuff, I just wish them luck

Edit: The reason I tried a3x originally is because of this topic... 

 

Edited August 20, 2019 by seadoggie01