Creating a .so file for plugins in ASPECT

Hi! I am a relatively new user to ASPECT and I am trying to learn how to make additional plugin files. I have ASPECT 2.4.0 -pre on my Virtual Machine and I am trying to run the following command on the terminal “cmake -DAspect_DIR=/path/to/aspect/build/ .
make” as mentioned in How to write a plugin — ASPECT 3.1.0-pre to make a .so file.

However, I am getting an error on giving the prompt “make”.
The screenshot is attached below.

Kindly guide me on how to resolve this error.
Thanks and regards,
Manusree

@Manusree Something is including the wrong file. Did you edit global.h? What is in line 25 referenced in the error message?
Best
W.

Thank You very much for your reply.

Yes, I did edit the global.h file. I changed the path of the global.h file from what it was before to where the file is actually located. But I’m not sure if I did that correctly.
Attached below is a screenshot of the global.h file


May I know how to proceed here onward?
Thanks again!
Manusree

Well, change it back, it was correct all along :slight_smile: You need the file that’s called config.h, not the one that’s called config.h.in. They’re not the same, and it’s not a surprise that things don’t compile :slight_smile:
Best
W.

Thank You very much for your kind help. I made the changes you suggested and I could create a .so file.
Thanks and regards,
Manusree

Hello! May I know how to compile an aspect plugin in the release mode?

Thanks and Regards,
Manusree

@Manusree You can just say make release in the directory in which your plugin is located, and then say make to actually compile it.
Best
W.

Wolfgang, I don’t think you need to switch build type for a plugin. If ASPECT is built in DebugRelease, the plugin will automatically compile both versions and pick the correct one at runtime.

So I said “make release” and then “make” and then I ran my prm file but it still doesn’t work.
May I know how to proceed?
Thanks and regards
Manusree

@tjhei Oh yes, I forgot that that’s how we do things now. Of course, I have no idea how we did that with @Manusree’s 2.4.0-pre version back in 2022…