Jump to content
Bowmore

Creating a list of all includes used by a script.

Recommended Posts

I've got a lot of AutoIt applications that I've written for work and I'm wanting to package the source for each of them in a zip file including all the includes and any dlls etc. The reason I want to do this is to enable minor tweaks to be quickly made to the applications in the future without having to worry about it not building due to some significant upgrade to one or more of the includes.

Before I start writing  myself a script to do this I would just like to check if anyone knows of script that will recursively parse all the  included in the main au3 file and produce a list of all include files the application is dependent on. 

 


"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning."- Rick Cook

Share this post


Link to post
Share on other sites

CodeScanner will produce a list of #includes; CodeCrypter creates a single script with no redundant parts (if so instructed).

Share this post


Link to post
Share on other sites

Thanks RTFC  CodeScanner is perfect for my needs, better than I was hoping for.


"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning."- Rick Cook

Share this post


Link to post
Share on other sites

I recommend archiving AutoIt's (ZIP) installers (https://www.autoitscript.com/autoit3/files/archive/autoit/autoit-v3.3.14.5.zip)

instead of archiving standard include files from all scripts.

It's simpler also for future running/compiling scripts with any different AutoIt's version,

in your scripts only add at first line comment about version of AutoIt needed for running/compiling that script.

See this my post about it:

 

Share this post


Link to post
Share on other sites

Zedna

Thanks for that suggestion I had not thought of doing that.  It's probably a simpler for me to include a zip of the installer with my code archive. 

Thanks


"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning."- Rick Cook

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...