Jump to content

Is there anything wrong with using gcc/mingw for plugins?


JRowe
 Share

Recommended Posts

I wanted to learn how to use gcc/mingw on my system and successfully built the plug-in sdk example. I was wondering if there was anything wrong with using mingw for plug-ins, such as there being some sort of system incompatibility, etc.

For those interested, install mingw, use the following to set your path (adapt if directory is different)

set Path=c:\MinGw\bin;%Path%

put the example.c in the au3_plugin_sdk directory, then use the following commands to build the dll in the same directory:

gcc -c -DBUILD_DLL au3plugin.c
gcc -c -DBUILD_DLL example.c
gcc -Wall -shared -o example.dll example.o au3plugin.o

I've read that mingw uses its own windows header, but I have no idea if that means conflict with AutoIt or if that fact is relatively meaningless in this context.

Also, is there anything wrong with the way I built the plugin dll?

Edited by JRowe
Link to comment
Share on other sites

Thank you :) I'm finding that the process is much less mystifying when I have to explicitly go through each .c file and compile the .o and then include it by hand to get my dll.

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...