Jump to content

Remove any link in compiled file to AutoIt?


ozone
 Share

Recommended Posts

Possibly a sensitive question. I don't know current C++ enough to program, but I know autoit very well. I've made an application I want to sell, and I made it using autoit. When I say "application" I mean I made a .au3 file that does some useful stuff and now want to sell the compiled exe.

So here is the question. Is there a way to remove the copyright notice and all the other info when you click on properties for the .exe file? If the authors of autoit don't want to allow that, then I won't argue. But I want to know if it's possible and if it's okay...

Link to comment
Share on other sites

I hope you are not of them (I read in the past) "bot-sellers" :ph34r:

Hmmm...I don't know if it is ok, in my opinion it is not.

<{POST_SNAPBACK}>

The world is full of wonderful people. And these wonderful people can do either legal or illegal things... so long as bot-selling is legal, then moral "values" should not be argued.
Link to comment
Share on other sites

The world is full of wonderful people. And these wonderful people can do either legal or illegal things... so long as bot-selling is legal, then moral "values" should not be argued.

<{POST_SNAPBACK}>

oddly enough, I'm with you there. I don't like bots, but that doesn't mean you shouldn't be able to make and sell them, as long as you're not infringing on someone else's rights... (Check the details of the license to make sure doing such isn't violating Jon's rights...) hold on a second...

SPECIAL EXCEPTION FOR COMPILED EXECUTABLES

==========================================

The stub (AutoItSC.bin) which is imbedded in each AutoIt compiled

script is part of AutoIt, and contains code that is under our copyright.

The terms of the GNU General Public License still apply as compiling

a script is a special form of linking with our stub.

Jonathan Bennett and the AutoIt team grant you special permission to

freely use and distribute all AutoIt compiled scripts (including

commercial ones), subject to the following restrictions:

1. You must compile your script with a completely unmodified AutoIt

version; either with our precompiled version, or (at your option)

with a self compiled version of the unmodified AutoIt sources as

distributed by us.

2. This also implies that the AutoIt stub must be completely unmodified

(with the exception of the stub file version information that you MAY

modify if you wish).

ANNOTATIONS

===========

- You can use a modified AutoIt version or modified AutoIt stub only for

programs that are compatible with the GNU General Public License.

- We grant you special permission to freely use and distribute all AutoIt

compiled programs.

- You can integrate all or part of AutoIt into projects that are compatible

with the GNU GPL, but obviously you cannot grant any special exceptions

beyond the GPL for our code in your project.

So, it looks like if you make your app GNU GPL Complient you can modify the bin to change the name, but that doing so without being GNU GPL complient would be wrong.

ANYWAYS, still not arguing against bots, just arguing against violating Jon and the team's rights.

"I'm not even supposed to be here today!" -Dante (Hicks)

Link to comment
Share on other sites

  • Administrators

I'm ok for people to change the version info of compiled exe via AutoItSC.bin. I'd actually like to provide the option to do it within Aut2Exe but haven't got around to it yet.

Link to comment
Share on other sites

I'm ok for people to change the version info of compiled exe via AutoItSC.bin.  I'd actually like to provide the option to do it within Aut2Exe but haven't got around to it yet.

<{POST_SNAPBACK}>

So maybe you aught to include that permission in the annotations of the license?

"I'm not even supposed to be here today!" -Dante (Hicks)

Link to comment
Share on other sites

I'm ok for people to change the version info of compiled exe via AutoItSC.bin.  I'd actually like to provide the option to do it within Aut2Exe but haven't got around to it yet.

<{POST_SNAPBACK}>

What would one use to edit that? Looks like it's encrypted.
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...